-----Original Message-----
From: Hannes Domani via Mingw-w64-public
Sent: Thursday, January 18, 2018 10:11 PM
To: mingw-w64-public@lists.sourceforge.net
Cc: Hannes Domani
Subject: Re: [Mingw-w64-public] How to backtrace a crash with gdb on Windows
7
(gdb) run
Starting program: C:\_64\comp\mpfr_bug\ggdb\mpfr-4.0.0\tests\tfprintf.exe
[New Thread 4680.0x160c]
This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.
repl-vsnprintf.c:358: GNU MP assertion failed: 0
[Inferior 1 (process 4680) exited with code 03]
(gdb) bt
No stack.
That's because it didn't crash, but an assertion failed.
This calls abort(), which then normally exits with exit code 3.
A crash looks in gdb like this:
Thread 1 received signal SIGSEGV, Segmentation fault.
To get a proper stacktrace for an assertion failure, just use "break
abort"
before "run".
Aaah ... yes, that makes all the difference.
Thank you, Hannes.
Cheers,
Rob
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
