* gdb and breakpoints in shared library
@ 2003-04-24 1:18 wim delvaux
0 siblings, 0 replies; only message in thread
From: wim delvaux @ 2003-04-24 1:18 UTC (permalink / raw)
To: gdb
Hi all,
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 ?
Comments ?
W
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-04-24 1:18 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-24 1:18 gdb and breakpoints in shared library wim delvaux
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).