This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [rfc] Print solib events in mi-mode
> For the case where stop-on-shlibs-added is not set, we have an MI
> notification that gets posted each time a shared library is loaded. It
> looks like this to the UI side:
>
> =shlibs-updated
> =shlibs-added,shlib-info=[num="54",name="SKTDrawDocument.ob",kind="-
> ",dyld-addr="0x271000",reason="dyld",requested-
> state="?",state="N",path="/Developer/Examples/AppKit/Sketch/build/
> Sketch.build/Sketch
> (Upgraded).build/Objects-normal/ppc/
> SKTDrawDocument.ob",slide="",addr="",prefix=""]
> ~"Re-enabling shared library breakpoints: 1\n"
> <-
> =shlibs-added,shlib-info=[num="55",name="SKTGraphic.ob",kind="-",dyld-
> addr="0x28a000",reason="dyld",requested-state="?",state="N",path="/
> Developer/Examples/AppKit/Sketch/build/Sketch.build/Sketch
> (Upgraded).build/Objects-normal/ppc/
> SKTGraphic.ob",slide="",addr="",prefix=""]
>
>
> In our case, this message is emitted by one of our arch-specific files,
> macosx/macosx-nat-dyld.c, in a function called macosx_solib_add().
Good idea, unfortunately we're mostly using the generic svr4 stuff. I
probably COULD do it in our backend but the problem is that this is not QNX
specific. It needs to be a standard part of GDB because the Eclipse CDT is
going to rely on it.
> The future-break patches were posted at least once in the past along
> with the save-breakpoints command; I can find a URL ref if anyone
> cares.
I read that thread. Very interesting. This is one of those cases where it
would be nice to have the functionality in gdb but the IDE should be able to
do it easier as long as it has notification. It should be fairly easy to
get notification from gdb but it doesn't look like Daniel wants people to
rely on stop-on-solib-events so he won't let me mi-ificate it.
cheers,
Kris