Re: Segfault in current bzr

[Eli Zaretskii <eliz@gnu.org>]

> Date: Tue, 28 Sep 2010 13:10:23 +0200
> From: grischka <grishka@gmx.de>
> Cc: emacs-devel@gnu.org
> 
> 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

  (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.