From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] [gdb/testsuite] Fix FAIL in gdb.base/annota1.exp
Date: Wed, 6 Oct 2021 16:51:38 -0400 [thread overview]
Message-ID: <e1aad51c-10b9-a9e9-09ae-d46a2f223797@simark.ca> (raw)
In-Reply-To: <20211006153307.15868-2-tdevries@suse.de>
On 2021-10-06 11:33 a.m., Tom de Vries via Gdb-patches wrote:
> On openSUSE tumbleweed I run into:
> ...
> FAIL: gdb.base/annota1.exp: run until main breakpoint (timeout)
> ...
> due to a message related to libthread_db:
> ...
> ^Z^Zstarting^M
> [Thread debugging using libthread_db enabled]^M
> Using host libthread_db library "/lib64/libthread_db.so.1".^M
> ^M
> ^Z^Zframes-invalid^M
> ...
> which is not matched by the regexp.
>
> Fix this by updating the regexp.
>
> Tested on x86_64-linux.
The patches LGTM. Do you know why you see this message for a single
threaded program? Is it related to gcc/glibc now always linking against
libpthread (or libpthread being merged into libc, I don't remember)?
Simon
next prev parent reply other threads:[~2021-10-06 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 15:33 [PATCH 1/2] [gdb/testsuite] Refactor regexp " Tom de Vries
2021-10-06 15:33 ` [PATCH 2/2] [gdb/testsuite] Fix FAIL " Tom de Vries
2021-10-06 20:51 ` Simon Marchi [this message]
2021-10-07 3:43 ` Tom de Vries
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=e1aad51c-10b9-a9e9-09ae-d46a2f223797@simark.ca \
--to=simark@simark.ca \
--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).