From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [gdbserver] Problems trying to resume dead threads
Date: Mon, 04 Aug 2008 18:30:00 -0000 [thread overview]
Message-ID: <20080804182930.GA23825@caradoc.them.org> (raw)
In-Reply-To: <200808041823.m74INFCJ008291@d12av02.megacenter.de.ibm.com>
On Mon, Aug 04, 2008 at 08:23:14PM +0200, Ulrich Weigand wrote:
> Hmm, still fails with my Cell test case like this:
> writing register 25: No such process
> ptrace(regsets_fetch_inferior_registers) PID=14241: No such process
> reading register 0: No such process
:-( It must depend on where you are in gdbserver when the process is
killed. I hadn't thought about that.
Perhaps we should downgrade all these errors to warnings for errno ==
ESRCH?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-08-04 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 17:17 Ulrich Weigand
2008-08-04 13:40 ` Daniel Jacobowitz
2008-08-04 18:25 ` Ulrich Weigand
2008-08-04 18:30 ` Daniel Jacobowitz [this message]
2008-08-04 19:46 ` Ulrich Weigand
2008-08-04 19:55 ` Daniel Jacobowitz
2008-08-05 21:06 ` Ulrich Weigand
2008-08-05 21:59 ` Daniel Jacobowitz
2008-08-05 22:15 ` Ulrich Weigand
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=20080804182930.GA23825@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.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