This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC: Fix "break *EXP thread NUM"
- From: Daniel Jacobowitz <drow at false dot org>
- To: "Maciej W. Rozycki" <macro at codesourcery dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, Andrew Stubbs <ams at codesourcery dot com>, gdb-patches at sourceware dot org, Vladimir Prus <vladimir at codesourcery dot com>, Eli Zaretskii <eliz at gnu dot org>
- Date: Tue, 1 Dec 2009 15:03:52 -0500
- Subject: Re: RFC: Fix "break *EXP thread NUM"
- References: <20091123212736.GA3828@caradoc.them.org> <4B0BB652.3080303@codesourcery.com> <20091124142406.GA14875@caradoc.them.org> <20091124145422.GA26004@adacore.com> <20091124150533.GA8964@caradoc.them.org> <20091125204303.GA21726@caradoc.them.org> <alpine.DEB.1.10.0912011949050.22393@tp.orcam.me.uk>
On Tue, Dec 01, 2009 at 07:53:37PM +0000, Maciej W. Rozycki wrote:
> 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?
It's been discussed before, but no one has ever sat down to do the
work.
--
Daniel Jacobowitz
CodeSourcery