From: Claus Baumgartner <claus.baumgartner@netsonic.fi>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>,
Claus Baumgartner <claus.baumgartner@netsonic.fi>,
gdb@sourceware.org
Subject: Re: gdbserver i386_linux hardware watchpoints in a multi threaded application
Date: Fri, 17 Aug 2007 14:15:00 -0000 [thread overview]
Message-ID: <46C5AD8B.9050104@netsonic.fi> (raw)
In-Reply-To: <20070815192547.GA1168@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Wed, Aug 15, 2007 at 04:12:29PM -0300, Luis Machado wrote:
>> On Wed, 2007-08-15 at 21:38 +0300, Claus Baumgartner wrote:
>>> Hi,
>>>
>>> I implemented the hardware watchpoints for the i386 linux target in the
>>> gdbserver and it works fine in the same thread where the watchpoint
>>> has been assigned. I would like to use gdb and gdb server to debug
>>> memory locations overwritten by other threads and this is where gdb fails.
>>>
>>> Is there any work in progress regarding this?
>> Yes, there is. The patch Jeff Johnston wrote some time ago should
>> address this on GDB. I'm currently taking over his work and adding
>> support for ppc.
>
> I think that Jeff's patches only affect gdb native debugging, and
> gdbserver would need an independent fix. But the same solution should
> work there, too.
>
> Claus, do you have a copyright assignment? Are you interested in
> contributing the i386 watchpoint support for gdbserver?
>
I'm overloaded for the moment and the i386 watchpoint support is quite
messy. I will send a patch when I get the time to clean it up.
Have a nice day,
Claus
prev parent reply other threads:[~2007-08-17 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 18:39 Claus Baumgartner
2007-08-15 19:12 ` Luis Machado
2007-08-15 19:25 ` Daniel Jacobowitz
2007-08-17 14:15 ` Claus Baumgartner [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=46C5AD8B.9050104@netsonic.fi \
--to=claus.baumgartner@netsonic.fi \
--cc=gdb@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.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