From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/29206] 0.187: test suite fails with core dumped in run-backtrace-native*.sh
Date: Tue, 31 May 2022 13:54:36 +0000 [thread overview]
Message-ID: <bug-29206-10460-7LhMeoz6Ec@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29206-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29206
--- Comment #4 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Letu Ren from comment #3)
> I just installed glibc-debug package as the debug symbol in ArchLinux and
> rebuilt the package. Tests of run-backtrace-native*.sh are successful
Great. Then this part is a duplicate of bug #29176
> but
> several new tests are failed. I attached the new test-suite.log as the
> attachment. Are these failure intended?
No, in theory the testsuite is all PASS.
I am not sure what is going wrong with these other tests.
It looks like the testcases themselves are not compiled with -g. So they don't
contain debuginfo. Might that be the case?
> Sorry for reporting duplicate issues. It's my first time to report a bug on
> sourceware bugzilla.
No worries. Thanks for the report.
> Last question, how can I know the patch for this issue has been applied?
> Just wait for a new release note or somehow to be added to a CC list?
Best to add yourself to the CC list of the relevant bug(s). Then you'll get a
notification when a patch is proposed and/or committed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-05-31 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 11:27 [Bug general/29206] New: " fantasquex at gmail dot com
2022-05-31 12:11 ` [Bug general/29206] " mark at klomp dot org
2022-05-31 12:37 ` fantasquex at gmail dot com
2022-05-31 12:44 ` fantasquex at gmail dot com
2022-05-31 13:54 ` mark at klomp dot org [this message]
2022-05-31 14:14 ` fantasquex at gmail dot com
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=bug-29206-10460-7LhMeoz6Ec@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).