From: Daniel Jacobowitz <drow@false.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Randolph Chung <randolph@tausq.org>, gdb@sources.redhat.com
Subject: Re: [RFC] what to do with hpux-specific solib features
Date: Tue, 07 Dec 2004 00:24:00 -0000 [thread overview]
Message-ID: <20041207002418.GA1143@nevyn.them.org> (raw)
In-Reply-To: <20041206171507.3c7c0d51.kevinb@redhat.com>
On Mon, Dec 06, 2004 at 05:15:07PM -0700, Kevin Buettner wrote:
> On Mon, 6 Dec 2004 15:01:05 -0800
> Randolph Chung <randolph@tausq.org> wrote:
>
> > There are a bunch of features that are only implemented currently for
> > the SOM and pa64 solib handlers for HP-UX. Do we want to support these
> > elsewhere? do we want to get rid of them?
> >
> > e.g.
> > Dynamically-linked library events may be caught:
> > catch load - loads of any library
> > catch load <libname> - loads of a particular library
> > catch unload - unloads of any library
> > catch unload <libname> - unloads of a particular library
>
> This provides a more fine grained way of stopping on particular events
> than "set stop-on-solib-events", right?
>
> It seems to me that this functionality might occasionally be useful
> elsewhere. However, I wouldn't let that hold you up if you're
> attempting to convert over to the generic solib machinery. It seems
> to me that such functionality could be implemented in a generic
> fashion (by noticing when a shared library is added to or removed from
> the global list), and as such, could be added back at any time.
And, IMO, should be. Along with a way to print what libraries have
been loaded or unloaded. I've wanted this quite often.
Completely agree about reimplementing them later instead of now, if
it's more convenient.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-12-07 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 23:01 Randolph Chung
2004-12-07 0:15 ` Kevin Buettner
2004-12-07 0:24 ` Daniel Jacobowitz [this message]
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=20041207002418.GA1143@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=randolph@tausq.org \
/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