Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/doco] Document task-specific breakpoints
Date: Fri, 27 Mar 2009 15:50:00 -0000	[thread overview]
Message-ID: <u8wmrm0v4.fsf@gnu.org> (raw)
In-Reply-To: <20090327153441.GP9472@adacore.com>

> Date: Fri, 27 Mar 2009 08:34:41 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> "Running"
> is another one of these states which just says that, from the
> point of view of the program, that this task is not waiting
> for an event, nor sleeping, nor waiting for a rendez-vous, etc.
> It's simply executing some code.

But in fact, it isn't executing some code, it's stopped at a
breakpoint, isn't it?  If it is executing code, what code is that?

> > OK, but I think the "running" part should be either fixed or
> > explained.
> 
> I think that "Running" is fine and doesn't need fixing.

If I were the user looking at the "Running" status, I'd certainly
think that something is dead wrong with this task-specific breakpoint.


  reply	other threads:[~2009-03-27 15:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 22:02 Joel Brobecker
2009-03-25 22:11 ` Joel Brobecker
2009-03-26 13:10   ` Eli Zaretskii
2009-03-26 22:50     ` Joel Brobecker
2009-03-27 11:56       ` Eli Zaretskii
2009-03-27 15:39         ` Joel Brobecker
2009-03-27 15:50           ` Eli Zaretskii [this message]
2009-03-27 16:11             ` Tom Tromey
2009-03-27 16:36             ` Joel Brobecker
2009-03-27 16:59               ` Joel Brobecker
2009-03-27 18:47               ` Eli Zaretskii
2009-04-09 16:47       ` Tom Tromey
2009-04-09 16:59         ` Joel Brobecker
2009-04-09 17:19           ` Eli Zaretskii
2009-04-09 17:33             ` Joel Brobecker
2009-04-09 17:40               ` Eli Zaretskii
2009-04-09 20:14                 ` Joel Brobecker
2009-03-31 18:31   ` Joel Brobecker
2009-03-31 20:20     ` Eli Zaretskii

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=u8wmrm0v4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.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