Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: kevinb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] new command: maintenance print target-stack
Date: Sun, 22 Oct 2006 20:03:00 -0000	[thread overview]
Message-ID: <200610222003.k9MK3QPN023611@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20061020100100.49fb9285@ironwood.lan> (message from Kevin 	Buettner on Fri, 20 Oct 2006 10:01:00 -0700)

> Date: Fri, 20 Oct 2006 10:01:00 -0700
> From: Kevin Buettner <kevinb@redhat.com>
> 
> On Tue, 17 Oct 2006 18:52:47 -0400
> Joel Brobecker <brobecker@adacore.com> wrote:
> 
> > While working to "auto-solib-add", I found that I was very frequently
> > in need to dumping the current target stack (I just need the names),
> > to see if the multi-thread layer has been pushed or not. So I
> > implemented a new "maintenance" command, hoping that others might
> > find it useful.
> > 
> >         (gdb) maintenance print target-stack 
> >         The current target stack is:
> >           - multi-thread (multi-threaded child process.)
> >           - child (Unix child process)
> >           - exec (Local exec file)
> >           - None (None)
> > 
> > Opinions? Eventually, we might want to actually dump more
> > information if that's useful to others, but that's a start.
> 
> As a developer, I know that I'd find this to be useful from time to
> time.  I'm in favor of this patch.

No objections from me either.  I don't think we make any guarantees
about the availibility of the maintenance commands, so we can always
improve this later (if necessary).

Mark


      reply	other threads:[~2006-10-22 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 22:52 Joel Brobecker
2006-10-20 17:01 ` Kevin Buettner
2006-10-22 20:03   ` Mark Kettenis [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=200610222003.k9MK3QPN023611@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@redhat.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