From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/29767] run-backtrace-native-core{,-biarch}.sh Tests Fail
Date: Tue, 13 Dec 2022 14:15:43 +0000 [thread overview]
Message-ID: <bug-29767-10460-i7frlEfsf5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29767-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29767
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #6 from Mark Wielaard <mark at klomp dot org> ---
I don't fully understand what is going wrong here.
The issue is "No modules recognized in core file" error which is produced when
dwfl_core_file_report return zero.
A zero return means no modules were found from inspecting the core file.
Would it be possible to see if the core file produced (inside the test dir) is
still there and attach it to this bug report for manual inspection?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-13 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 16:27 [Bug general/29767] New: " shahab.vahedi at gmail dot com
2022-11-09 16:27 ` [Bug general/29767] " shahab.vahedi at gmail dot com
2022-11-09 16:28 ` shahab.vahedi at gmail dot com
2022-11-09 16:29 ` shahab.vahedi at gmail dot com
2022-11-09 16:29 ` shahab.vahedi at gmail dot com
2022-11-09 16:29 ` shahab.vahedi at gmail dot com
2022-11-09 16:30 ` shahab.vahedi at gmail dot com
2022-12-13 14:15 ` mark at klomp dot org [this message]
2022-12-16 15:47 ` shahab.vahedi at gmail dot com
2022-12-16 22:33 ` mark at klomp dot org
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-29767-10460-i7frlEfsf5@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).