This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [non-stop] 01/10 Add "executing" property
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <pedro at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 16 Jun 2008 00:47:43 +0300
- Subject: Re: [non-stop] 01/10 Add "executing" property
- References: <200806152203.14626.pedro@codesourcery.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Sun, 15 Jun 2008 22:03:14 +0100
>
> The "running" thread property recently added represents the frontend view
> of the thread running state. While doing a step for instance, the inferior
> starts/stops several times while single-stepping. ÂWe only clear
> the "running" state of the inferior when it does a normal_stop.
> This patch adds a new field, that altough similar to "running"
> has a different usage. ÂIt replaces the current target_executing
> global with a similar per-thread concept. ÂInferior and frame/stack
> control then can then use this property to know when it is possible
> to read registers and memory from a thread.
Thanks, but isn't any of the significant changes in these series of
patches worthy of being mentioned in gdbint.texinfo?
> * Makefile.in (event-top.o, frame.o, inf-loop.o, top.o):
> Update.
I think you should tell what prerequisites were added to each target.
A simple "update" will never reveal when a prerequisite was added, if
someone will ever want to know.