D.gnu - [Bug 98] New: MinGW: stack trace on exception needs enhanced
- gdc-bugzilla gdcproject.org (60/60) Feb 01 2014 http://bugzilla.gdcproject.org/show_bug.cgi?id=98
http://bugzilla.gdcproject.org/show_bug.cgi?id=98 Summary: MinGW: stack trace on exception needs enhanced Classification: Unclassified Product: GDC Version: development Platform: x86 OS/Version: MinGW Status: NEW Severity: minor Priority: Normal Component: gdc AssignedTo: ibuclaw gdcproject.org ReportedBy: slavo5150 yahoo.com Daniel Green created an issue 2012-06-12 ***************************************** 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. ../../../../gcc-4.6.1/libphobos/libdruntime/gcc/deh.d:153 ../../../../gcc-4.6.1/libphobos/libdruntime/core/exception.d:421 ../../../../gcc-4.6.1/libphobos/libdruntime/rt/dmain2.d:203 ../../../../gcc-4.6.1/libphobos/libdruntime/rt/dmain2.d:574 at ../../../../gcc-4.6.1/libphobos/libdruntime/rt/dmain2.d:549 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. 40FF74 409BDB 411176 418F0F 411382 401659 4126A2 411FE1 41271E 411FE1 <- last GDB entry 411D35 401735 4013CE 4014E8 -- Configure bugmail: http://bugzilla.gdcproject.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
Feb 01 2014