You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -302,4 +302,9 @@ aqt install-tool windows desktop tools_ifw
302
302
303
303
# How to analyse crashlog
304
304
305
-
:building_construction: Under construction :building_construction:
305
+
:warning: This methos is for Windows only.
306
+
307
+
- Get `DFTFringe.exe.debug` file corresponding to the release where the log comes from in github
308
+
- Run `addr2line -e DFTFringe.exe.debug 0x00000000005A7229` with the address of the stack you get from the log
309
+
- You should get an output like `D:\a\DFTFringe\DFTFringe\DFTFringe/./boost/stacktrace/stacktrace.hpp:78`
310
+
- Do this for each line of the call stack leading to the crash. Look at corresponding file and line (here it's `stacktrace.hpp` line `78`) of the source code corresponding to the release you are debugging to understand what went wrong.
0 commit comments