From: Andrew Cagney <ac131313@redhat.com>
To: "Howell, David P" <david.p.howell@intel.com>
Cc: Scott Moser <ssmoser@us.ibm.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] plugin patch
Date: Wed, 06 Nov 2002 11:12:00 -0000 [thread overview]
Message-ID: <3DC969B5.6030003@redhat.com> (raw)
In-Reply-To: <331AD7BED1579543AD146F5A1A44D5251279DE@fmsmsx403.fm.intel.com>
>> GDB via runtime loaded shared libraries in ways that may not fit with
>> the direction of the main GDB tree (not cross-platform, not stable,
>> niche audience...).
>
> For folks like myself that are working on an alternate architecture or
> runtime support components (in this case NGPT threads) this would be
> very useful, as I can see several info commands that I would like to
> add for M:N user mode scheduling state and LWP state display that would
> be unique to NGPT and it's implementation.
I suspect that if NGPT needs additional thread specific info commands
then other thread implementations will be interested in similar.
Extending the command set in a generic way also means that a user will
find a consistent interface that works across thread implementations.
Cf, ``info vector'' which works (well should work) across Altivec, e500
and i386.
> Instead of having to add this to the standard gdb as a one-off for NGPT,
> I can use the standard gdb and design them as plug-ins to be loaded only
>
> when debugging NGPT applications. This feels a lot cleaner and could be
> applied for other gdb features/architectures to keep the core as small
> and efficient as possible, loading additional support/features on demand
> only when needed.
That is the theory already. Reality differs though, there is always
more work to do :-(. That work is, however, independant of a plug-in
module.
Andrew
next prev parent reply other threads:[~2002-11-06 19:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 7:47 Howell, David P
2002-11-06 7:55 ` Daniel Jacobowitz
2002-11-06 11:12 ` Andrew Cagney [this message]
2002-11-06 11:55 ` Paul A. Clarke
2002-11-06 12:29 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2002-10-28 14:01 Scott Moser
2002-10-28 22:28 ` Eli Zaretskii
2002-10-29 7:55 ` Paul A. Clarke
2002-11-06 6:45 ` Scott Moser
2002-11-06 6:56 ` Jelmer Vernooij
2002-11-06 7:13 ` Scott Moser
2002-11-06 7:54 ` Jelmer Vernooij
2002-11-06 9:14 ` Andrew Cagney
2002-11-06 15:07 ` Paul A. Clarke
2002-11-06 15:56 ` Andrew Cagney
2002-11-07 10:05 ` Paul A. Clarke
2002-11-07 11:57 ` Andrew Cagney
2002-11-07 13:10 ` Klee Dienes
2002-11-06 15:56 ` 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=3DC969B5.6030003@redhat.com \
--to=ac131313@redhat.com \
--cc=david.p.howell@intel.com \
--cc=gdb-patches@sources.redhat.com \
--cc=ssmoser@us.ibm.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