From: Daniel Jacobowitz <drow@false.org>
To: David L <idht4n@hotmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Couldn't write debug register: No such process
Date: Wed, 05 Oct 2005 19:06:00 -0000 [thread overview]
Message-ID: <20051005190602.GA11412@nevyn.them.org> (raw)
In-Reply-To: <BAY104-F15723AADA3C41B387EB10E84820@phx.gbl>
On Wed, Oct 05, 2005 at 12:02:32PM -0700, David L wrote:
> (gdb) target remote localhost:9005
> Remote debugging using localhost:9005
> 0x00add7c0 in ?? ()
> (gdb) watch *((double *) 0x8155218)
> Hardware watchpoint 1: *(double *) 135615000
> (gdb) cont
> Continuing.
> Couldn't write debug register: No such process.
>
> I'm not sure if it's ok to add a watchpoint like I did, but it works when I
> don't use gdbserver. I did it like this because adding a watchpoint like
> this:
Gdbserver doesn't support watchpoints for x86, unfortunately.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-10-05 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 20:05 David L
2005-10-05 5:31 ` Ramana Radhakrishnan
2005-10-05 13:02 ` Daniel Jacobowitz
2005-10-05 19:03 ` David L
2005-10-05 19:06 ` Daniel Jacobowitz [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=20051005190602.GA11412@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=idht4n@hotmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).