MinGW: stack trace on exception needs enhanced

Daniel Green avatarDaniel Green created an issue

D introduced a stack trace feature on exceptions. Currently, this will only list address of the function and no additional information.

This should be enhanced for MinGW 32/64 to return better output for GDC.

The MinGW64 version would also crash upon execution of StackWalk64 after a Fiber context switch.

This occurred on the first call(suggestive that is a windows issue?) and may have been related to unapplied Windows Updates.

However, due to the following stack disappearance with GDB this will remain disabled until it this issue has been resolved or proof that it was a Microsoft bug.

#0  _d_throw (obj=...) at ../../../../gcc-4.6.1/libphobos/libdruntime/gcc/deh.d:153
#1  0x0000000000420853 in onAssertErrorMsg (file=..., line=53, msg=...) at ../../../../gcc-4.6.1/libphobos/libdruntime/core/exception.d:421
#2  0x0000000000411382 in _d_assert_msg (msg=..., file=) at ../../../../gcc-4.6.1/libphobos/libdruntime/rt/dmain2.d:203
#3  0x0000000000401659 in D main () at issue342.d:53
#4  0x00000000004126a2 in rt.dmain2._d_run_main.runMain (this=0x22fda0) at ../../../../gcc-4.6.1/libphobos/libdruntime/rt/dmain2.d:574
#5  0x0000000000411fe1 in rt.dmain2._d_run_main.tryExec (this=0x22fda0, dg=...) at ../../../../gcc-4.6.1/libphobos/libdruntime/rt/dmain2.d:549
#6  0x0000000000000000 in ?? () <- This is invalid.  Where's the rest of the call stack?

When compared to the values given by StackWalk64. It's missing 4 frames of stack information lost upon calling rt.dmain2._d_run_main.tryExec. Prior to the use of Fibers. This symptom was not exhibited by MinGW32.

411FE1 <- last GDB entry

Comments (2)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.