Red Hat Bugzilla – Bug 53672
libdl.so causes gdb to miss breakpoints
Last modified: 2007-04-18 12:37:08 EDT
LTC 254 Hardware Environment: x86 Software Environment: RedHat 7.x (even tried a recent beta 7.2) works on RedHat 6.x, SuSE, Debian Steps to Reproduce: 1. create blah.c: echo "int main() { return 0; }" >blah.c 2. compile: $ gcc -o blah blah.c 3. $ gdb ./blah 4. (gdb) break main 5. (gdb) run 6. Note that it successfully hits the breakpoint... 7. (gdb) quit 8. compile: $ gcc -o blah blah.c -ldl 9. repeat steps 3-5 10. Note that the breakpoint is missed, and gdb prints a number of error messages. Actual Results: breakpoint at main() is missed, and error messages from gdb Expected Results: breakpoint hit (no error messages) Contact Information: pacman@us.ibm.com (Paul Clarke) alternate contact: smoser@us.ibm.com (Scott Moser) Additional Information: We also brought /lib/libdl-2.2.4.so from a Debian and this problem went away. The machines on which the failure occured has /lib/libdl-2.2.2.so.
Jakub, this looks glibc related?
Does not look like that very much. It is reproduceable with our libdl-2.2.4.so too. Without debugging gdb I cannot say what's going on and why gdb becomes confused. Certainly it is not clear from gdb strace.
Fixed in gdb-5.0.91rh-1