This is the mail archive of the
mailing list for the GDB project.
gdb and breakpoints in shared library
- From: wim delvaux <wim dot delvaux at adaptiveplanet dot com>
- To: gdb at sources dot redhat dot com
- Date: Thu, 24 Apr 2003 02:57:34 +0200
- Subject: gdb and breakpoints in shared library
Following situation in gdb 5.3 on Linux glibc 2.3
load a program with dynamically loaded shared libraries (using dlopen)
do some navigation and end up in some source location in some shared library
set a breakpoint on that location (in that shared library)
rerun the program (restart it)
gdb then produces some 'errors' not being able to set a shared library.
This goes on until the library again gets loaded using dlopen. Then the
breakpoint can be set.
However Often the breakpoint gets lost and is not set OR is not active.
so 2 questions.
Why the error message. If the breakpoint cannot be set ... ok that's it ...
Why does gdb looses shlib breakpoints Is there a 'max errors' count that
once the number of errors is exceeded completely ignores the breakpoint ?