From 0d6b9bb9304bcee1cbee139d6f04633b1cb3b698 Mon Sep 17 00:00:00 2001 From: Julien Staub Date: Fri, 16 May 2025 18:27:12 +0200 Subject: [PATCH 1/2] add missing section to readme --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index c4f01b5d..9d11eb09 100644 --- a/README.md +++ b/README.md @@ -302,4 +302,9 @@ aqt install-tool windows desktop tools_ifw # How to analyse crashlog -:building_construction: Under construction :building_construction: +:warning: This methos is for Windows only. + +- Get `DFTFringe.exe.debug` file corresponding to the release where the log comes from in github +- Run `addr2line -e DFTFringe.exe.debug 0x00000000005A7229` with the address of the stack you get from the log +- You should get an output like `D:\a\DFTFringe\DFTFringe\DFTFringe/./boost/stacktrace/stacktrace.hpp:78` +- 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. From 6f3d4490e6d2d605fb49ec8202529fd5479af965 Mon Sep 17 00:00:00 2001 From: Julien Staub Date: Fri, 16 May 2025 18:31:40 +0200 Subject: [PATCH 2/2] typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9d11eb09..efa8ff00 100644 --- a/README.md +++ b/README.md @@ -302,7 +302,7 @@ aqt install-tool windows desktop tools_ifw # How to analyse crashlog -:warning: This methos is for Windows only. +:warning: This method is for Windows only. - Get `DFTFringe.exe.debug` file corresponding to the release where the log comes from in github - Run `addr2line -e DFTFringe.exe.debug 0x00000000005A7229` with the address of the stack you get from the log