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: Thu, 26 Mar 2009 13:10:00 -0000	[thread overview]
Message-ID: <uwsacnc65.fsf@gnu.org> (raw)
In-Reply-To: <20090325220236.GF9472@adacore.com>

> Date: Wed, 25 Mar 2009 15:02:36 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> 
> As promised when I sent the code patches for task-specific breakpoints,
> here is the associated documentation.

Thanks.

> 2009-03-25  Joel Brobecker  <brobecker@adacore.com>
> 
>         * gdb.texinfo (Ada Tasks): Add documentation about task-specific
>         breakpoints.
> 
> OK to commit?

Yes, with a few comments:

> +@cindex breakpoints and tasks

Suggest to mention Ada explicitly:

  @cindex breakpoints and tasks, in Ada

> +@cindex task breakpoints

Likewise.

> +@kindex break @dots{} task @var{taskno}

Similarly:

  @kindex break @dots{} task @var{taskno}@r{ (Ada)}

> +@var{linespec} specifies source lines, as described
> +in @ref{Set Breaks,,Setting breakpoints}.

It is better to point to "Specify Location", where @var{linespec} is
_really_ described.

> +Breakpoint 5, test_task_debug.tB.1 (_task=0x11ffffc60)
                                ^^^^^
What is this part?  Should we explain it in some footnote?  And what
about _task=0x11ffffc60 part, should it perhaps be explained, too?

> +(@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?

Finally, please add a cross-reference to here in the "Set Breaks"
node, saying that Ada supports thread-specific breakpoints.

Thanks.


  reply	other threads:[~2009-03-26  4:25 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 [this message]
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
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=uwsacnc65.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