public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "fantasquex at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/29206] New: 0.187: test suite fails with core dumped in run-backtrace-native*.sh
Date: Tue, 31 May 2022 11:27:46 +0000	[thread overview]
Message-ID: <bug-29206-10460@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29206

            Bug ID: 29206
           Summary: 0.187: test suite fails with core dumped in
                    run-backtrace-native*.sh
           Product: elfutils
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: general
          Assignee: unassigned at sourceware dot org
          Reporter: fantasquex at gmail dot com
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

Created attachment 14125
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14125&action=edit
config.log and test-suite.log

I tried to rebuild elfutils package of ArchLinux and noticed one
test(run-backtrace-native.sh) failed. And I tried to build the package manually
to reproduce the failure and got one more failure run-backtrace-native-core.sh.
After searching previous bug reports, I noticed two related reports(#28190 and
#28263) which are both marked as resolved but their error message are slightly
different from mine. So I decide to file a bug.

CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions        
-Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security        
-fstack-clash-protection -fcf-protection -g
-ffile-prefix-map=/build/elfutils/src=/usr/src/debug -flto=auto
-ffat-lto-objects
    CXXFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions      
  -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security        
-fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -g
-ffile-prefix-map=/build/elfutils/src=/usr/src/debug -flto=auto

FAIL: run-backtrace-native.sh
=============================

case 0: expected symname 'raise' got '(null)'
./test-subr.sh: line 84: 3249284 Aborted                 (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child: no main
FAIL run-backtrace-native.sh (exit status: 1)

Please let me know if you need more details or want me to perform some
diagnostics.
FAIL: run-backtrace-native-core.sh
==================================

/usr/bin/coredumpctl
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
           PID: 3249363 (backtrace-child)
           UID: 1015 (fanta)
           GID: 1015 (fanta)
        Signal: 6 (ABRT)
     Timestamp: Tue 2022-05-31 17:50:38 CST (1s ago)
  Command Line: /home/fanta/elfutils-0.187/tests/backtrace-child --gencore
    Executable: /home/fanta/elfutils-0.187/tests/backtrace-child
 Control Group: /user.slice/user-1015.slice/session-385.scope
          Unit: session-385.scope
         Slice: user-1015.slice
       Session: 385
     Owner UID: 1015 (fanta)
       Boot ID: e05e3117547d4e7586af9313885930db
    Machine ID: d4a40ce966aa4a93ae4df91c3b83aa21
      Hostname: shellder.felixc.at
       Storage:
/var/lib/systemd/coredump/core.backtrace-child.1015.e05e3117547d4e7586af9313885930db.3249363.1653990638000000.zst
(present)
     Disk Size: 22.9K
       Message: Process 3249363 (backtrace-child) of user 1015 dumped core.

                Module /home/fanta/elfutils-0.187/tests/backtrace-child with
build-id 4bf1f1c07341394a7478b89fbd0e69c3eb325dbe
                Module linux-vdso.so.1 with build-id
c4fab7a7ee86e62a6272cb22354ad5a06fbf1a5d
                Module ld-linux-x86-64.so.2 with build-id
fc93487393eea02b5bc6e76e48976fc325294c24
                Module libc.so.6 with build-id
388993b6ef62f964bc7bf473c069fbfe957b9e44
                Stack trace of thread 3249364:
                #0  0x00007f93ac9a336c n/a (libc.so.6 + 0x8e36c)
                #1  0x00007f93ac953838 raise (libc.so.6 + 0x3e838)
                #2  0x000055b9f1ab3352 n/a
(/home/fanta/elfutils-0.187/tests/backtrace-child + 0x1352)
                ELF object binary architecture: AMD x86-64
case 0: expected symname 'raise' got '(null)'
./test-subr.sh: line 84: 3249383 Aborted                 (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-core.3249363: no main
rmdir: failed to remove 'test-3249355': Directory not empty
FAIL run-backtrace-native-core.sh (exit status: 1)

Some important logs are listed above, and full logs(config.log test-suite.log)
are attached as attachment.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-05-31 11:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 11:27 fantasquex at gmail dot com [this message]
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
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@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).