From: Kevin Buettner <kevinb@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v5] [gdb/testsuite] New test: gdb.base/check-errno.exp
Date: Sat, 11 May 2024 12:30:06 -0700 [thread overview]
Message-ID: <20240511123006.2113c857@f40-zbm-amd> (raw)
In-Reply-To: <d7b139a0-12a8-4cc9-9fa1-425ac2da8b66@suse.de>
On Fri, 10 May 2024 10:40:42 +0200
Tom de Vries <tdevries@suse.de> wrote:
> Hi Kevin,
>
> I applied the patch and tested without and with debug info on leap 15.5,
> and only got passes and xfails, so that looks good. Likewise on tumbleweed.
>
> One nit:
> ...
> $ git show --check --pretty=%s
> New test: gdb.base/check-errno.exp
>
> gdb/testsuite/gdb.base/check-errno.exp:38: trailing whitespace.
> +# there were always scenarios in which printing errno was problematic.
> ...
Fixed (in my local tree).
> I tested this using make-check-all.sh, and got:
> ...
> (gdb) PASS: gdb.base/check-errno.exp: default: continue to breakpoint:
> main-breakpoint
> ptype errno^M
> Cannot find thread-local storage for Thread 14233.14233, shared library
> /lib64/libc.so.6:^M
> Remote target failed to process qGetTLSAddr request^M
> (gdb) FAIL: gdb.base/check-errno.exp: default: ptype errno
> ...
> with f.i. target board native-extended-gdbserver/native-gdbserver, I'm
> hoping that's easy to fix in the test-case.
Fixed - and yes, it was easy.
Thanks for the review.
Kevin
next prev parent reply other threads:[~2024-05-11 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 21:10 Kevin Buettner
2024-05-10 8:40 ` Tom de Vries
2024-05-11 19:30 ` Kevin Buettner [this message]
2024-05-10 13:08 ` Pedro Alves
2024-05-11 21:57 ` Kevin Buettner
2024-05-13 14:34 ` Pedro Alves
2024-05-10 13:12 ` Pedro Alves
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=20240511123006.2113c857@f40-zbm-amd \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).