|
From: | grischka |
Subject: | Re: Segfault in current bzr |
Date: | Tue, 28 Sep 2010 19:19:14 +0200 |
User-agent: | Thunderbird 2.0.0.23 (Windows/20090812) |
Eli Zaretskii wrote:
Date: Tue, 28 Sep 2010 13:10:23 +0200 From: grischka <address@hidden> Cc: address@hidden Typically emacs: They're rather able to give people a lecture about gcc options than to add a simple one-line wrapper for abort to print the file:linenumber.Aha, and then we will see something like this: #1 0x00000000004ebc25 in abort () at emacs.c:427#2 0x00000000deadbeef in abort_wrapper (file=<value optimized out>, line=<value optimized out>) at grishka.c:1234#3 0x00000000005a5dd9 in wait_reading_process_output (time_limit=<value optimized out>, microsecs=<value optimized out>, read_kbd=-1, do_display=<value optimized out>, wait_for_cell=<value optimized out>, wait_proc=0x0, just_wait_proc=0)at process.c:5072
No, you'd see: emax: internal error at process.c:5072. Aborting. Which while you just started to preach the user how to use gcc and gdb might very well suffice for someone else to be done with the problem already. --- grischka
(gdb) frame 2#2 0x000000000045babe in abort_wrapper (file=<value optimized out>, line=<value optimized out>) at grishka.c:1234(gdb) print file No symbol "file" in current context. (gdb) print line No symbol "line" in current context. (gdb) Very useful, very informative. Debugging an optimized build is practically impossible, with current versions of GCC. End of story.
[Prev in Thread] | Current Thread | [Next in Thread] |