-
Notifications
You must be signed in to change notification settings - Fork 13
Reporting bugs
If you are reporting a bug then it can be useful to include a memory dump of the application so that the bug can be investigated, this is most useful if the application crashes or freezes. Please be sure when reporting an issue with a memory dump to report the exact version of AuTerm you are using from the releases page.
Run AuTerm as normal until you get to the point of the freeze, open task manager and go to the AuTerm process, right click it and select "Create memory dump". Once created click the open location button, this will show the memory dump file.
Follow the instructions on https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps to enable crash dump logs, then run AuTerm and cause the crash. The memory dump file should be located in %LOCALAPPDATA%\CrashDumps
Building from source is a preferred way of debugging as release builds are stripped to reduce file size. This requires Qt (including modules), GDB and build tools for your distro. With them installed, build AuTerm in debug mode, then run the output executable in GDB e.g.:
gdb ./AuTerm
run
Perform the tasks needed to freeze the application up or crash it, if it freezes then go to GDB and press ctrl + c, then enter the command bt and press enter to get a backtrace, attach this output to the bug report.
Ensure GDB is installed on your system, run AuTerm in GDB using:
gdb ./AuTerm
run
Perform the tasks needed to freeze the application up or crash it, if it freezes then go to GDB and press ctrl + c, then enter the command bt and press enter to get a backtrace, attach this output to the bug report.
Memory dump files should be compressed using e.g. 7zip, then uploaded somewhere that can be accessed without a login or account and attached to the bug report.