From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: gdb@sourceware.org
Subject: Re: linux-low.c: stop_all_processes vs longjmp snafu?
Date: Sun, 14 Dec 2008 18:32:00 -0000 [thread overview]
Message-ID: <20081214183121.GA28806@caradoc.them.org> (raw)
In-Reply-To: <e394668d0812131123k3b83077y60692d062f0c8e2f@mail.gmail.com>
On Sat, Dec 13, 2008 at 11:23:44AM -0800, Doug Evans wrote:
> I was thinking that we don't want to support nested setjmps. But in a
> case like this do we want to continue to try to stop all processes
> even if stopping one of them throws an error? [assuming we're keeping
> setjmp and not rewriting gdbserver in c++ ...]
I'm more thinking that we should do actual error handling in
gdbserver, and ditch the longjmp based version. It almost never
works. It tends to leave state inconsistent; and up until recently
(or maybe still) it left the protocol state machine in the wrong state.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-12-14 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 0:14 Doug Evans
2008-12-13 19:24 ` Doug Evans
2008-12-14 18:32 ` 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=20081214183121.GA28806@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
/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