This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: MI: "set stop-on" and stop reason


On Mon, Jan 30, 2006 at 12:08:50PM +0300, Vladimir Prus wrote:
> 
> 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).

I had to go look up what you meant since I'm not used to that spelling;
for anyone following along at home, that's stop-on-solib-events.  In my
opinion, the solib mechanism should implement catch load and catch
unload where possible.  Then, set stop-on-solib-events 1 can behave
like a general "catch load", and we can give it a new stop reason.

-- 
Daniel Jacobowitz
CodeSourcery


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]