public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "werner at suse dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/29327] A SIGSEGV in hardware optimized memset for sse2 __memset_sse2_unaligned_erms()
Date: Mon, 11 Jul 2022 08:15:03 +0000 [thread overview]
Message-ID: <bug-29327-131-3mgWZjawNT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29327-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29327
--- Comment #13 from Dr. Werner Fink <werner at suse dot de> ---
(In reply to H.J. Lu from comment #11)
> Please use LD_AUDIT to print out RDX and RDI for memset.
... I've tried that with exporting
LD_AUDIT=/lib64/libmemusage.so:/lib64/libc.so.6 in gdb (without `=' and `set
environment`) as well as with preloading /lib64/libmemusage.so but this shows
(gdb) set environment LD_AUDIT /lib64/libmemusage.so:/lib64/libc.so.6
(gdb) set environment LD_PRELOAD /lib64/libmemusage.so
(gdb) set environment MEMUSAGE_OUTPUT /dev/null
(gdb) set environment MEMUSAGE_TRACE_MMAP yes
(gdb) run
Starting program: /usr/lib64/kodi/kodi.bin
During startup program terminated with signal SIGSEGV, Segmentation fault.
using a core dump shows with coredumpctl
Message: Process 2029 (kodi.bin) of user 223 dumped core.
Module /usr/lib64/kodi/kodi.bin with build-id
e1ff57cc18fdbfb94f9c868d0390ae072a644e1a
Module /usr/lib64/libc.so.6 with build-id
712c0cad2c922965a1c0d127ae86a118675ff13a
Module /usr/lib64/libmemusage.so with build-id
1e3a860bf330a7dbf351bdf99fc7d54bdf78338e
Module /usr/lib64/ld-linux-x86-64.so.2 with build-id
97b21d01a6af70cd365d50707e35559701f446ac
Module linux-vdso.so.1 with build-id
8afe55b49ea313a498cf2943d1ed322dd2573036
Stack trace of thread 2029:
#0 0x00007fb5b14a32fc ___dlsym (/usr/lib64/libc.so.6 +
0xa32fc)
#1 0x00007fb5b17fab31 me (/usr/lib64/libmemusage.so + 0x1b31)
#2 0x00007fb5b199418e call_init
(/usr/lib64/ld-linux-x86-64.so.2 + 0x818e)
#3 0x00007fb5b199428c _dl_init
(/usr/lib64/ld-linux-x86-64.so.2 + 0x828c)
#4 0x00007fb5b19a9df8 _dl_catch_exception
(/usr/lib64/ld-linux-x86-64.so.2 + 0x1ddf8)
#5 0x00007fb5b199b5e6 dl_open_worker
(/usr/lib64/ld-linux-x86-64.so.2 + 0xf5e6)
#6 0x00007fb5b19a9db9 _dl_catch_exception
(/usr/lib64/ld-linux-x86-64.so.2 + 0x1ddb9)
#7 0x00007fb5b199b9cc _dl_open
(/usr/lib64/ld-linux-x86-64.so.2 + 0xf9cc)
#8 0x00007fb5b19acc2e dlmopen_doit
(/usr/lib64/ld-linux-x86-64.so.2 + 0x20c2e)
#9 0x00007fb5b19a9db9 _dl_catch_exception
(/usr/lib64/ld-linux-x86-64.so.2 + 0x1ddb9)
#10 0x00007fb5b19a9e63 _dl_catch_error
(/usr/lib64/ld-linux-x86-64.so.2 + 0x1de63)
#11 0x00007fb5b19b0332 load_audit_module
(/usr/lib64/ld-linux-x86-64.so.2 + 0x24332)
#12 0x00007fb5b19abf7f _dl_sysdep_start
(/usr/lib64/ld-linux-x86-64.so.2 + 0x1ff7f)
#13 0x00007fb5b19ade9e _dl_start_final
(/usr/lib64/ld-linux-x86-64.so.2 + 0x21e9e)
#14 0x00007fb5b19acb98 _start (/usr/lib64/ld-linux-x86-64.so.2
+ 0x20b98)
ELF object binary architecture: AMD x86-64
but gdb shows with this core
Reading symbols from /usr/lib64/kodi/kodi.bin...
Reading symbols from
/usr/lib/debug/usr/lib64/kodi/kodi.bin-19.4-2.14.x86_64.debug...
[New LWP 2029]
Core was generated by `/usr/lib64/kodi/kodi.bin'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fb5b14a32fc in ?? ()
(gdb) bt
#0 0x00007fb5b14a32fc in ?? ()
#1 0x0000000000000007 in ?? ()
#2 0x00007fb5b1458872 in ?? ()
#3 0x00007fb5b1988440 in ?? ()
#4 0x00007fb5b17fdce0 in ?? ()
#5 0x0000000000000001 in ?? ()
#6 0xce7c2412b4499900 in ?? ()
#7 0x00007ffd4fd8bc48 in ?? ()
#8 0x0000000000000000 in ?? ()
(gdb) quit
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-11 8:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 11:54 [Bug libc/29327] New: " werner at suse dot de
2022-07-07 11:55 ` [Bug libc/29327] " werner at suse dot de
2022-07-07 11:56 ` werner at suse dot de
2022-07-07 12:07 ` werner at suse dot de
2022-07-07 17:50 ` [Bug string/29327] " fweimer at redhat dot com
2022-07-07 18:24 ` goldstein.w.n at gmail dot com
2022-07-07 18:52 ` goldstein.w.n at gmail dot com
2022-07-07 19:26 ` goldstein.w.n at gmail dot com
2022-07-07 20:03 ` hjl.tools at gmail dot com
2022-07-07 20:10 ` goldstein.w.n at gmail dot com
2022-07-08 12:03 ` werner at suse dot de
2022-07-08 12:26 ` werner at suse dot de
2022-07-08 12:29 ` werner at suse dot de
2022-07-08 14:29 ` hjl.tools at gmail dot com
2022-07-08 15:50 ` goldstein.w.n at gmail dot com
2022-07-11 8:15 ` werner at suse dot de [this message]
2022-07-11 8:23 ` werner at suse dot de
2022-07-11 14:10 ` hjl.tools at gmail dot com
2022-07-12 7:02 ` werner at suse dot de
2022-07-12 7:12 ` werner at suse dot de
2022-07-12 7:20 ` werner at suse dot de
2022-07-12 14:47 ` hjl.tools at gmail dot com
2022-07-12 15:46 ` hjl.tools at gmail dot com
2022-07-13 9:22 ` werner at suse dot de
2022-07-13 14:30 ` hjl.tools at gmail dot com
2022-07-13 15:47 ` goldstein.w.n at gmail dot com
2022-07-14 7:36 ` werner at suse dot de
2022-07-14 15:42 ` hjl.tools at gmail dot com
2022-07-19 9:58 ` werner at suse dot de
2022-07-19 17:47 ` hjl.tools at gmail dot com
2022-07-22 11:04 ` werner at suse dot de
2022-07-22 11:13 ` werner at suse dot de
2022-07-22 14:26 ` goldstein.w.n at gmail dot com
2022-07-25 6:00 ` werner at suse dot de
2022-07-25 14:20 ` werner at suse dot de
2022-07-28 11:44 ` bww9643 at gmail dot com
2022-07-28 11:46 ` bww9643 at gmail dot com
2022-08-09 12:46 ` werner at suse dot de
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-29327-131-3mgWZjawNT@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).