From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>
Subject: Re: Use is_stopped, instead of !is_running
Date: Tue, 29 Jul 2008 16:32:00 -0000 [thread overview]
Message-ID: <200807291732.08263.pedro@codesourcery.com> (raw)
In-Reply-To: <1217347148.5842.7.camel@localhost.localdomain>
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
next prev parent reply other threads:[~2008-07-29 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 13:59 Pedro Alves
2008-07-29 15:59 ` Thiago Jung Bauermann
2008-07-29 16:32 ` Pedro Alves [this message]
2008-08-09 14:31 ` Joel Brobecker
2008-08-16 23:54 ` Pedro Alves
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=200807291732.08263.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@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