From: Daniel Jacobowitz <daniel.jacobowitz@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>,
Stan Shebs <stanshebs@earthlink.net>,
gdb@sourceware.org
Subject: Re: Toward multicore GDB - Set theory
Date: Tue, 08 Nov 2011 01:14:00 -0000 [thread overview]
Message-ID: <CAN9gPaFjXgogT7iEDL8zdgxaWjG6iW1SHDKqPdrOkbfupCz1eg@mail.gmail.com> (raw)
In-Reply-To: <20111107173729.GD335@adacore.com>
On Mon, Nov 7, 2011 at 12:37 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>
> > I think in the past we talked about square brackets and prefix.
> > How about we consider that as a straw proposal?
> >
> > (gdb) [0-13] print x
>
> I like this option best.
>
Me, too. I expect this to be a power user feature and plumbing for
IDEs; you won't very often want to specify this stuff by hand. But if
we make it easy to name groups of threads, then the abbreviations may
be more commonly used. Ideally I'd like to be able to hook this with
Python, so that a new thread can be categorized in some
application-specific way.
For example, it's common in the program I work on to have pools of
threads for a specific purpose. You don't always want to treat the
request processing threads and the RPC threads the same way, but you
don't care which request processing thread hits your breakpoint - and
they can be created and destroyed dynamically.
--
Thanks,
Daniel
next prev parent reply other threads:[~2011-11-08 1:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 0:04 Stan Shebs
2011-11-03 21:01 ` Tom Tromey
2011-11-04 13:20 ` Pedro Alves
2011-11-07 17:38 ` Joel Brobecker
2011-11-08 1:14 ` Daniel Jacobowitz [this message]
2011-11-08 5:17 ` Matt Rice
2011-11-08 14:50 ` Pedro Alves
2011-11-08 15:04 ` Tom Tromey
2011-11-08 15:45 ` Pedro Alves
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=CAN9gPaFjXgogT7iEDL8zdgxaWjG6iW1SHDKqPdrOkbfupCz1eg@mail.gmail.com \
--to=daniel.jacobowitz@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=stanshebs@earthlink.net \
--cc=tromey@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