The Abysmal State of Debugging Under Linux
Date: 26/10/2003
This happens all the time:
lemon% gdb ./scribe
GNU gdb Red Hat Linux (5.3post-0.20021129.18rh)
Copyright 2003 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-gnu"...
(gdb) r
Starting program: /home/lemon/matthew/Lgi/Scribe/scribe
[New Thread 1078238400 (LWP 10623)]
Screen: 1600 x 1200 @ 24 bpp
InScribe v1.86 (Test43, Linux v2.4, Debug, Kde)
[New Thread 1086864688 (LWP 10640)]
[Thread 1086864688 (zombie) exited]
[New Thread 1097809200 (LWP 10644)]
[New Thread 1116949808 (LWP 10647)]
[New Thread 1125342512 (LWP 10648)]
[New Thread 1133735216 (LWP 10649)]
[Thread 1116949808 (zombie) exited]
[Thread 1125342512 (zombie) exited]
Couldn't get registers: No such process.
(gdb) q
The program is running.  Exit anyway? (y or n) y
"No such process" AND "The program is running"... great... just great. The application just 'exits' somewhere... who knows... gdb won't tell. However it runs fine outside the debugger. So the debugger is screwing up the execution environment so programs exit at strange points. I LOVE gdb... it's the best! *vomit*

So most of the time, to debug non-trivial applications on this supposedly "enterprise ready" operating system you are left with printf.

Super! I love printf!
Email (optional): (Will be HTML encoded to evade harvesting)
Remember username and/or email in a cookie.
Notify me of new posts in this thread via email.