Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [DOC] Mention what happens when the thread of a thread-specific breakpoint is gone.
Date: Fri, 04 Oct 2013 17:49:00 -0000	[thread overview]
Message-ID: <83y569apvb.fsf@gnu.org> (raw)
In-Reply-To: <1380898896-16767-1-git-send-email-palves@redhat.com>

> From: Pedro Alves <palves@redhat.com>
> Date: Fri,  4 Oct 2013 16:01:36 +0100
> 
> We recently made GDB auto-delete thread-specific breakpoints when the
> corresponding thread is gone, but we haven't mentioned it in the manual.
> 
> OK?

Yes, thanks.  One nit, though:

> +Thread-specific breakpoints are automatically deleted when
> +@value{GDBN} detects the corresponding thread is gone.
                                          ^^^^^^^^^^^^^^
I'd say "thread exits" instead.


  reply	other threads:[~2013-10-04 17:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 15:01 Pedro Alves
2013-10-04 17:49 ` Eli Zaretskii [this message]
2013-10-04 17:54   ` Pedro Alves
2013-10-04 17:59     ` Pedro Alves
2013-10-04 18:26       ` Pedro Alves
2013-10-04 19:20         ` Eli Zaretskii
2013-10-07 11:03           ` Thread-specific breakpoints: say "no longer in the thread list" instead of "gone". (was: [PATCH] [DOC] Mention what happens when the thread of a thread-specific breakpoint is gone.) Pedro Alves
2013-10-07 11:14           ` [PATCH] [DOC] Mention what happens when the thread of a thread-specific breakpoint is gone Pedro Alves
2013-10-04 18:14     ` 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=83y569apvb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /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