From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Doug Evans <dje@google.com>, Marc Khouzam <marc.khouzam@ericsson.com>
Subject: Re: More descriptive prompt [was Re: Process exit in multi-process, and gdb's selected thread.]
Date: Tue, 24 Feb 2009 19:09:00 -0000 [thread overview]
Message-ID: <200902241909.16678.pedro@codesourcery.com> (raw)
In-Reply-To: <200902241841.11813.pedro@codesourcery.com>
On Tuesday 24 February 2009 18:41:11, Pedro Alves wrote:
> On Tuesday 24 February 2009 18:12:03, Doug Evans wrote:
> > If there's general favorability of this I'll work on a patch.
To be clear, I meant to say that I do favor a way to have a
more descriptive prompt, however it ends up implemented. I'd be
fine with python, or whatever.
> This was something that had occured to be before as well when
> I got tired of doing "info threads" while working on non-stop.
>
> This is what I was using at one point. It added a PS1 style
> formatting to the gdb command, so I could do
>
> (gdb) set prompt (\\p \\T: \\S)
>
> And have the prompt show up as:
>
> (1 Thread 0x7ffff7fd36e0 (LWP 12690): stopped)
>
> or, ...
>
> (1 Thread 0x7ffff7fd36e0 (LWP 12690): running)
>
> etc.
>
--
Pedro Alves
next prev parent reply other threads:[~2009-02-24 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 18:12 Doug Evans
2009-02-24 18:26 ` Daniel Jacobowitz
2009-02-24 18:41 ` Pedro Alves
2009-02-24 19:09 ` Pedro Alves [this message]
2009-02-25 17:41 ` Joel Brobecker
2009-02-25 17:49 ` Doug Evans
2009-02-25 17:59 ` Paul Pluzhnikov
2009-02-25 18:52 ` More descriptive prompt Tom Tromey
2009-02-25 19:00 ` Doug Evans
2009-02-25 19:42 ` Tom Tromey
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=200902241909.16678.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.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