This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
MI and pending breakpoints
- From: Vladimir Prus <ghost at cs dot msu dot su>
- To: gdb at sources dot redhat dot com
- Date: Wed, 15 Mar 2006 15:25:02 +0300
- Subject: MI and pending breakpoints
Hello!
I've got some problems with "pending breakpoints" functionality, using MI
interface. Here's example session:
(gdb) break helper.cpp:4
break helper.cpp:4
No source file named helper.cpp.
Breakpoint 2 (helper.cpp:4) pending.
^done
(gdb) -break-insert helper.cpp:5
No source file named helper.cpp.
^done
The CLI command correctly adds pending breakpoint. The helper.cpp file is in
dlopen-ed shared library, and the breakpoint will be resolved when the
library is loaded.
The MI command neither errors out (the reply is "^done", not "^error"), nor
it does anything. It does not report breakpoint number, it does not add any
breakpoint at all.
What is the reason for this? Is this a bug? How do other frontend authors
deal with breakpoints in shared libraries, then?
Thanks in advance,
Volodya