When running gdb on a Qt application, the program will
segfault in vfprintf when printing an initial debug message.
Here's the last two entries in the stack
#0 0x404dd5a8 in main_arena () from /lib/libc.so.6
#1 0x4043df06 in buffered_vfprintf (s=0x404dd500,
format=0x40171ca0 "Qt: gdb: -nograb added to command-line
options.\n\t Use the -dograb option to enforce grabbing.",
args=0xbffff2ac) at vfprintf.c:1752
I set the priority to low because you can get around this by
starting the program with "run -nograb". It seems like it
might be indicative of larger problems, though.
The program below will demonstrate the problem. It will run
normally (do nothing) from a command line, but dies when run
int main( int argc, char** argv )
Verified. GDB 4.18 can debug this program without problems. I really
suggest we get an update for gdb out the door for 6.0 asap. It isn't
just Qt -- anyone debugging moderately complex C++ applications cannot
debug with Red Hat Linux 6.0.
*** Bug 1772 has been marked as a duplicate of this bug. ***
1. Get the binary at the given URL.
2. gunzip it and run 'gdb linux-midi' (does not need to be run).
3. Type 'print CORBA_tk_null'.
Voila, core dump.
As an aside, why doesn't the package in 5.9 have the x86 hardware breakpoint support? The 5.2 package did.
------- Additional Comments From email@example.com 07/12/99 11:12 -------
There is no DNS entry for
Does this test case have a new location?
Please try gdb-4.18-3 which is now in Rawhide.