Re: how to get backtrace on warnings?

[Dave Morse <dm-gtk bomberlan net>]

Hmmmmmm... Still no joy.  Here's a transcript.  Its puzzling that it
prints out "Breakpoint 1 at 0x813fc38" during the running of the program,
but doesn't actually wake up the interactive debugging prompt.  Perhaps
gdb can't find the source for gdk, and thus automatically continues?


 GNU gdb 19991004
 Copyright 1998 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you are
 welcome to change it and/or distribute copies of it under certain conditions.
 Type "show copying" to see the conditions.
 There is absolutely no warranty for GDB.  Type "show warranty" for details.
 This GDB was configured as "i386-redhat-linux"...
 (gdb) break gdk_x_error
 Breakpoint 1 at 0x813fc38
 (gdb) break g_warning
 Function "g_warning" not defined.
 (gdb) break g_log
 Breakpoint 2 at 0x8168d0b: file gmessages.c, line 407.
 (gdb) break g_logv
 Breakpoint 3 at 0x8168a32: file gmessages.c, line 336.
 (gdb) run --gnome-options --sync --g-fatal-warnings
 Starting program: /home/dm/coco/copter-commander --gnome-options --sync --g-fatal-warnings
 Breakpoint 1 at 0x813fc38
 Breakpoint 1 at 0x40516145
[TIME PASSES, MENUS GET CLICKED, ETC]
 Gdk-ERROR **: BadValue (integer parameter out of range for operation)
   serial 8747 error_code 2 request_code 130 minor_code 9

 Program exited with code 01.
 (gdb) darn