From: "Kris Warkentin" <kewarken@qnx.com>
To: "Jason Molenda" <jmolenda@apple.com>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: [rfc] Print solib events in mi-mode
Date: Thu, 10 Jul 2003 12:23:00 -0000 [thread overview]
Message-ID: <0a6c01c346de$15ba22b0$0202040a@catdog> (raw)
In-Reply-To: <55757AD0-B24D-11D7-9281-000393D457E2@apple.com>
> 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
next prev parent reply other threads:[~2003-07-10 12:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 20:35 Kris Warkentin
2003-07-08 21:02 ` Andrew Cagney
2003-07-09 12:24 ` Kris Warkentin
2003-07-09 15:09 ` Daniel Jacobowitz
2003-07-09 15:38 ` Kris Warkentin
2003-07-09 16:24 ` Daniel Jacobowitz
2003-07-09 17:29 ` Kris Warkentin
2003-07-09 17:41 ` Kevin Buettner
2003-07-09 17:49 ` Kris Warkentin
2003-07-09 18:01 ` Kris Warkentin
2003-07-09 18:05 ` Daniel Jacobowitz
2003-07-09 18:21 ` Kris Warkentin
2003-07-09 18:30 ` Daniel Jacobowitz
2003-07-09 19:12 ` Kris Warkentin
2003-07-09 19:46 ` Daniel Jacobowitz
2003-07-09 20:00 ` Kris Warkentin
2003-07-09 20:03 ` Daniel Jacobowitz
2003-07-18 16:12 ` Andrew Cagney
2003-07-09 20:38 ` Jason Molenda
2003-07-10 12:23 ` Kris Warkentin [this message]
2003-07-10 16:33 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='0a6c01c346de$15ba22b0$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=gdb@sources.redhat.com \
--cc=jmolenda@apple.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox