From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
Andrew Stubbs <ams@codesourcery.com>,
gdb-patches@sourceware.org,
Vladimir Prus <vladimir@codesourcery.com>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: RFC: Fix "break *EXP thread NUM"
Date: Tue, 01 Dec 2009 19:53:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.0912011949050.22393@tp.orcam.me.uk> (raw)
In-Reply-To: <20091125204303.GA21726@caradoc.them.org>
On Wed, 25 Nov 2009, Daniel Jacobowitz wrote:
> > Meanwhile, here's a patch that handles "t" and "task". I talked to
> > Andrew about this, and I still think we can get away without "+N" and
> > "-N"; they're only accepted by an accident of strtol.
>
> I have checked this in.
While we are at it -- it may be worth thinking about propagating thread
information associated with breakpoints and watchpoints down to the
respective backends. Some processors (like the MIPS 34K multi-threaded
core) supports thread qualification for execution and data breakpoints in
hardware and debug stubs would be eager to make use of that for
performance gain. Has it been considered before?
Maciej
next prev parent reply other threads:[~2009-12-01 19:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 21:27 Daniel Jacobowitz
2009-11-24 0:21 ` Joel Brobecker
2009-11-24 10:33 ` Andrew Stubbs
2009-11-24 14:24 ` Daniel Jacobowitz
2009-11-24 14:54 ` Joel Brobecker
2009-11-24 15:05 ` Daniel Jacobowitz
2009-11-25 20:43 ` Daniel Jacobowitz
2009-12-01 19:53 ` Maciej W. Rozycki [this message]
2009-12-01 20:04 ` Daniel Jacobowitz
2010-01-01 6:31 ` [commit] Fix "break *EXP thread/task NUM" for Ada (was: "Re: RFC: Fix "break *EXP thread NUM"") Joel Brobecker
2009-11-24 17:08 ` RFC: Fix "break *EXP thread NUM" 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=alpine.DEB.1.10.0912011949050.22393@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=ams@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@codesourcery.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