This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: Stand resume() on its head
- From: Kevin Buettner <kevinb at redhat dot com>
- To: Andrew Cagney <ac131313 at redhat dot com>, gdb-patches at sources dot redhat dot com
- Date: Tue, 5 Nov 2002 13:46:46 -0700
- Subject: Re: Stand resume() on its head
- References: <3DC829E3.4090603@redhat.com>
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