From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Stand resume() on its head
Date: Tue, 05 Nov 2002 12:46:00 -0000 [thread overview]
Message-ID: <1021105204646.ZM27982@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "Stand resume() on its head" (Nov 5, 3:28pm)
On Nov 5, 3:28pm, Andrew Cagney wrote:
> There have now been several discussion threads that lead to the
> conclusion that
>
> target->resume (ptid_t, int, enum target_signal)
>
> needs changing. At present the suggestion is to add a parameter to
> indicate schedule locking and similar operations.
>
> I'd like to propose a different approach. Instead of passing to
> resume() what to do, have resume() iterate over all the threads asking
> each what it should do - suspend, step, run, signal, ...
Sounds reasonable. (In fact, it seems a whole lot more workable than
the other approach.)
Kevin
next prev parent reply other threads:[~2002-11-05 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 12:28 Andrew Cagney
2002-11-05 12:46 ` Kevin Buettner [this message]
2002-11-05 14:57 ` Andrew Cagney
2002-11-05 12:59 ` Daniel Jacobowitz
2002-11-05 14:15 ` Michael Snyder
2002-11-05 20:03 ` Daniel Jacobowitz
2002-11-05 15:10 ` Andrew Cagney
2002-11-05 14:10 ` Michael Snyder
2002-11-05 15:14 ` Andrew Cagney
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=1021105204646.ZM27982@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.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