From: Pedro Alves <pedro@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: gdb@sourceware.org
Subject: Re: call_function_by_hand doesn't restore target async?
Date: Thu, 04 Dec 2008 22:14:00 -0000 [thread overview]
Message-ID: <200812042214.23358.pedro@codesourcery.com> (raw)
In-Reply-To: <e394668d0812041336w4a76a857g116e1eeb9bd020de@mail.gmail.com>
On Thursday 04 December 2008 21:36:31, Doug Evans wrote:
> On Thu, Dec 4, 2008 at 1:23 PM, Pedro Alves <pedro@codesourcery.com> wrote:
> > In practice, and
> > especially with non-stop mode, making infcalls async is ranging somewhere
> > from hard to impossible.
>
> If that's the general consensus, at least for now, would there be any
Dunno if that's the consensus; I'd really love it if someone proved me wrong.
> objection to submitting a patch that has call_function_by_hand invoke
> proceed() in a TRY_CATCH? After cleaning things up it could rethrow.
I don't object in principle, but I'm no foreteller either. :-)
--
Pedro Alves
prev parent reply other threads:[~2008-12-04 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 20:19 Doug Evans
2008-12-04 21:23 ` Pedro Alves
2008-12-04 21:33 ` Pedro Alves
2008-12-04 21:37 ` Doug Evans
2008-12-04 22:14 ` Pedro Alves [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=200812042214.23358.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--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