public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
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 13:02:00 -0000	[thread overview]
Message-ID: <20051005130209.GA705@nevyn.them.org> (raw)
In-Reply-To: <BAY104-F17C3A7820DD8CE69B0D84E84830@phx.gbl>

On Tue, Oct 04, 2005 at 01:04:58PM -0700, David L wrote:
> I'm getting this error when I try to continue after setting a remote target 
> (gdbserver on a local socket).  I'm using gdb 6.3 that I compiled from 
> source on a fedora core 3 system.
> 
> Couldn't write debug register: No such process
> 
> 
> What does this mean?  Thanks...

That something is broken.  There's not enough information in your
report to say more.  Is the gdbserver also running on an IA32 GNU/Linux
platform?  What's the transcript of the session look like?

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  parent reply	other threads:[~2005-10-05 13:02 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 [this message]
2005-10-05 19:03   ` David L
2005-10-05 19:06     ` Daniel Jacobowitz

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=20051005130209.GA705@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).