This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Use is_stopped, instead of !is_running


On Tuesday 29 July 2008 16:59:08, Thiago Jung Bauermann wrote:
> If the thread state is not a boolean, then IMHO offering convenient
> functions which treat it as such and then putting a warning in the
> comment is really setting up a subtle trap for GDB hackers... :-)
>
> What about just nuking is_running and is_stopping, and making everybody
> use is_thread_state directly? That would make this reality explicit.

It might not look like it, but I'm doing baby steps in that
direction.  :-)

There are target_has_execution checks inside the is_XXX
functions that I'd like to cleanly get rid of.

-- 
Pedro Alves


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]