public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "shahab.vahedi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/29767] run-backtrace-native-core{,-biarch}.sh Tests Fail
Date: Fri, 16 Dec 2022 15:47:09 +0000	[thread overview]
Message-ID: <bug-29767-10460-66ZHx6FdmU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29767-10460@http.sourceware.org/bugzilla/>

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

--- Comment #7 from Shahab <shahab.vahedi at gmail dot com> ---
$$$$$$$$$$$$
$$ TL;DR; $$___________________________________________
$$$$$$$$$$$$

Please close the issue.

$$$$$$$$$$$$$$
$$ Rumbling $$_________________________________________
$$$$$$$$$$$$$$

I just tried it on:

9c136cb3 -- libdwfl: Read no more than required in dwfl_segment_report_module

and the tests don't fail anymore:

$ tail tests/test-suite.log

==========================================
   elfutils 0.188: tests/test-suite.log
==========================================

# TOTAL: 236
# PASS:  235
# SKIP:  1
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

SKIP: run-lfs-symbols.sh
========================

LFS testing is irrelevant on this system
SKIP run-lfs-symbols.sh (exit status: 77)

$ cat tests/run-backtrace-native-core.sh.log
0x7ffda79b0000  0x7ffda79b1000  linux-vdso.so.1
0x7fe4927a7000  0x7fe4927d3198  ld-linux-x86-64.so.2
0x7fe4925a6000  0x7fe49276b2a0  libc.so.6
0x7fe49276c000  0x7fe49278c1b0  libpthread.so.0
0x55f411477000  0x55f41147b0a8  backtrace-child
TID 20602:
# 0 0x7fe49277f7a1      raise
# 1 0x55f41147842d - 1  sigusr2
# 2 0x55f4114784fa - 1  stdarg
# 3 0x55f411478510 - 1  backtracegen
# 4 0x55f411478519 - 1  start
# 5 0x7fe492774eae - 1  start_thread
# 6 0x7fe4926a42ff - 1  __clone
TID 20601:
# 0 0x7fe492776447      __pthread_clockjoin_ex
# 1 0x55f41147825c - 1  main
# 2 0x7fe4925cde0a - 1  __libc_start_main
# 3 0x55f41147833a - 1  _start
# 1 0x55f41147825c - 1  main
PASS run-backtrace-native-core.sh (exit status: 0)


$ cat tests/run-backtrace-native-core-biarch.sh.log
0xf7edd000      0xf7edf000      linux-gate.so.1
0xf7edf000      0xf7f0c978      ld-linux.so.2
0xf7cb0000      0xf7e9ded8      libc.so.6
0xf7e9e000      0xf7ebe100      libpthread.so.0
0x5657c000      0x56580058      backtrace-child-biarch
TID 20630:
# 0 0xf7edd549          __kernel_vsyscall
# 1 0xf7eb2fb9 - 1      raise
# 2 0x5657d4ba - 1      sigusr2
# 3 0x5657d594 - 1      stdarg
# 4 0x5657d5aa - 1      backtracegen
# 5 0x5657d5b8 - 1      start
# 6 0xf7ea6501 - 1      start_thread
# 7 0xf7dcadb6 - 1      __clone
TID 20629:
# 0 0xf7edd549          __kernel_vsyscall
# 1 0xf7ea7d47 - 1      __pthread_clockjoin_ex
# 2 0xf7ea7a3c - 1      pthread_join
# 3 0x5657d288 - 1      main
# 4 0xf7ccef1a - 1      __libc_start_main
# 5 0x5657d371 - 1      _start
# 3 0x5657d288 - 1      main
PASS run-backtrace-native-core-biarch.sh (exit status: 0)

Relevant diff between the 2 config files:
--- /old/config.log
+++ /new/config.log
@@ -4,7 +4,7 @@
 It was created by elfutils configure 0.188, which was
 generated by GNU Autoconf 2.71.  Invocation command line was

-  $ ../configure --disable-debuginfod --disable-libdebuginfod --prefix=/usr
--enable-maintainer-mode
+  $ ../configure --disable-debuginfod --disable-libdebuginfod
--enable-maintainer-mode --prefix=/usr

 ## --------- ##
 ## Platform. ##
@@ -12,9 +12,9 @@

 hostname = sourceware
 uname -m = x86_64
-uname -r = 5.19.17_1
+uname -r = 6.0.11_1
 uname -s = Linux
-uname -v = #1 SMP PREEMPT_DYNAMIC Mon Oct 31 14:24:17 UTC 2022
+uname -v = #1 SMP PREEMPT_DYNAMIC Wed Dec 7 02:03:34 UTC 2022

 /usr/bin/uname -p = unknown
 /bin/uname -X     = unknown
@@ -39,6 +39,7 @@
 PATH: /sbin/
 PATH: /home/user/.rvm/bin/
 PATH: /home/user/.rvm/bin/
+PATH: /home/user/.rvm/bin/


 ## ----------- ##
@@ -1605,3 +1606,24 @@
 #define HAVE_PTHREAD_SETNAME_NP 1

 configure: exit 0
+
+## ---------------------- ##
+## Running config.status. ##
+## ---------------------- ##
+
+This file was extended by elfutils config.status 0.188, which was
+generated by GNU Autoconf 2.71.  Invocation command line was
+
+  CONFIG_FILES    =
+  CONFIG_HEADERS  =
+  CONFIG_LINKS    =
+  CONFIG_COMMANDS =
+  $ ./config.status backends/Makefile depfiles
+
+on sourceware
+
+config.status:1055: creating backends/Makefile
+config.status:1269: executing depfiles commands
+config.status:1344: cd backends       && sed -e '/# am--include-marker/d'
Makefile         | make -f - am--depfiles
+make[3]: Nothing to be done for 'am--depfiles'.
+config.status:1351: $? = 0

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

  parent reply	other threads:[~2022-12-16 15:47 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
2022-12-16 15:47 ` shahab.vahedi at gmail dot com [this message]
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-66ZHx6FdmU@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).