Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* [RFC] what to do with hpux-specific solib features
@ 2004-12-06 23:01 Randolph Chung
  2004-12-07  0:15 ` Kevin Buettner
  0 siblings, 1 reply; 3+ messages in thread
From: Randolph Chung @ 2004-12-06 23:01 UTC (permalink / raw)
  To: gdb

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

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RFC] what to do with hpux-specific solib features
  2004-12-06 23:01 [RFC] what to do with hpux-specific solib features Randolph Chung
@ 2004-12-07  0:15 ` Kevin Buettner
  2004-12-07  0:24   ` Daniel Jacobowitz
  0 siblings, 1 reply; 3+ messages in thread
From: Kevin Buettner @ 2004-12-07  0:15 UTC (permalink / raw)
  To: Randolph Chung; +Cc: gdb

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.

Kevin


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RFC] what to do with hpux-specific solib features
  2004-12-07  0:15 ` Kevin Buettner
@ 2004-12-07  0:24   ` Daniel Jacobowitz
  0 siblings, 0 replies; 3+ messages in thread
From: Daniel Jacobowitz @ 2004-12-07  0:24 UTC (permalink / raw)
  To: Kevin Buettner; +Cc: Randolph Chung, gdb

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-12-07  0:24 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-12-06 23:01 [RFC] what to do with hpux-specific solib features Randolph Chung
2004-12-07  0:15 ` Kevin Buettner
2004-12-07  0:24   ` Daniel Jacobowitz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox