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 11:56:00 -0000 [thread overview]
Message-ID: <uljqrmk0c.fsf@gnu.org> (raw)
In-Reply-To: <20090326223902.GL9472@adacore.com>
> Date: Thu, 26 Mar 2009 15:39:02 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> > > +(@value{GDBP}) info tasks
> > > + ID TID P-ID Pri State Name
> > > + 1 140022020 0 15 Child Activation Wait main_task
> > > +* 2 140045060 1 15 Running t2
> >
> > "Running"? shouldn't it be stopped at breakpoint?
>
> In practice, yes, it is stopped. But this information is printed
> from the point of view of the runtime. To the runtime, task "t2"
> is running.
Sorry, I don't understand. Can you elaborate?
> Attached is a new version of the documentation patch:
>
> * gdb.texinfo (Ada Tasks): Add documentation about task-specific
> breakpoints.
> (Set Breaks): Add reference to thread-specific and task-specific
> breakpoints.
OK, but I think the "running" part should be either fixed or
explained.
next prev parent reply other threads:[~2009-03-27 8:47 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 [this message]
2009-03-27 15:39 ` Joel Brobecker
2009-03-27 15:50 ` Eli Zaretskii
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=uljqrmk0c.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