From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: fix comment in gdb.threads/non-ldr-exit.exp
Date: Tue, 1 Dec 2020 10:54:00 +0100 [thread overview]
Message-ID: <0665b4b2-f704-4b85-df33-49e9a6301edc@suse.de> (raw)
In-Reply-To: <20201201045035.1206222-1-simon.marchi@polymtl.ca>
On 12/1/20 5:50 AM, Simon Marchi via Gdb-patches wrote:
> Maybe there's something I don't understand in that test, but the comment
> seems wrong. It checks what happens when the non-leader thread does an
> exit, not the leader.
>
I've checked both the semantics of the test-case and the commit log for
the commit adding the test-case, both agree with your observation, so LGTM.
Thanks,
- Tom
> gdb/testsuite/ChangeLog:
>
> * gdb.threads/non-ldr-exit.exp: Fix comment.
>
> Change-Id: I35c96a70c097fa9529737874f54f3f78036008a4
> ---
> gdb/testsuite/gdb.threads/non-ldr-exit.exp | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gdb/testsuite/gdb.threads/non-ldr-exit.exp b/gdb/testsuite/gdb.threads/non-ldr-exit.exp
> index 234d74dda1a3..522ddf602093 100644
> --- a/gdb/testsuite/gdb.threads/non-ldr-exit.exp
> +++ b/gdb/testsuite/gdb.threads/non-ldr-exit.exp
> @@ -13,7 +13,7 @@
> # You should have received a copy of the GNU General Public License
> # along with this program. If not, see <http://www.gnu.org/licenses/>.
>
> -# Exit of the thread group leader should not break GDB.
> +# Exit by a thread group non-leader should not break GDB.
>
> standard_testfile
> set executable ${testfile}
>
next prev parent reply other threads:[~2020-12-01 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 4:50 Simon Marchi via Gdb-patches
2020-12-01 9:54 ` Tom de Vries [this message]
2020-12-01 15:31 ` Simon Marchi via Gdb-patches
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=0665b4b2-f704-4b85-df33-49e9a6301edc@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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