MI: "set stop-on" and stop reason
Vladimir Prus
ghost@cs.msu.su
Mon Jan 30 12:16:00 GMT 2006
Hi!
As of gdb 6.4, the MI "stopped" packet does not include any "stopped due to
shared library load" reason amoung documented reasons. Here's what gdb
outputs when "set stop-on 1" is in effect and a shared library is loaded
(gdb)
set stop-on 1
&"set stop-on 1\n"
^done
(gdb)
-exec-run
^running
(gdb)
~"Stopped due to shared library event\n"
*stopped,thread-id="0"
(gdb)
Is is a defect, or by design (like "set stop-on" is deprecated, or
something).
- Volodya
More information about the Gdb
mailing list