Reporting ConEmu crashes
ConEmu is stable enough. But, unfortunately, any product may have yet unfixed problems. Please read the following if you find one.
- Third-party bugs
- ConEmu and ConEmuC processes
- Console applications
- Manual dump creation
ConEmu and ConEmuC processes
Well, if any unknown crash was occured in
MemoryDump may greatly help to locate and fix the problem.
ConEmuC.exe are handled automatically
and application suggests to user (message box) to create
MemoryDump (full or mini).
Due to limitation of issues attachments, please upload Zipped dumps to
DropBox or any other hosting and post the link
to issues or via email.
ConEmu does not handle crashes (exceptions actually) in the running console applications.
That is because to minimize intrusion to running application.
So, if some application crashes in ConEmu and do not crashes when you run it
in the standard Windows’ console started by
Win+R for example, please read
How to create required dump
For example, you observe a crash in
You have to set environment variable
ConEmuReportExe to that process name:
This may be done via:
- New console dialog. Example below sets
ConEmuReportExevariable and starts
set ConEmuReportExe=ls.exe & cmd.exe
- In some shells (
far) you may call
setdirectly from prompt.
Than, you may run you command from started console:
Message box must appears
At this time, call ConEmu’s System menu > Debug > Active process memory dump.
After pressing OK in “loaded” message box your error message expected. Save the dump. Upload Zipped dump to DropBox or any other hosting.
Manual dump creation
If you need to create dump manually (of any ConEmu’s processes or console application) please read that wiki.