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: Fri, 08 Jul 2022 12:26:52 +0000 [thread overview]
Message-ID: <bug-29327-131-FbXT8SUm3H@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 #9 from Dr. Werner Fink <werner at suse dot de> ---
(In reply to Noah Goldstein from comment #3)
> Are there any steps for reproduction?
I've tried the memusage script of glibc utils to debug memory consumption of
kodi Matric 19.4, this works like this:
export LD_PRELOAD=/lib64/libmemusage.so
export MEMUSAGE_OUTPUT=/dev/null
export MEMUSAGE_TRACE_MMAP=yes
but this make gdb a memory huge eating all physical RAM.
Therefore I tried to set the environment in gdb its self:
gdb --args /usr/lib64/kodi/kodi.bin
[...]
(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
Program terminated with signal SIGPROF, Profiling timer expired.
The program no longer exists.
(gdb) br memset
Breakpoint 1 at 0x705f80 (2 locations)
(gdb) run
Starting program: /usr/lib64/kodi/kodi.bin
Breakpoint 1, memset () at
../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:125
125 ENTRY (MEMSET_SYMBOL (__memset, unaligned))
(gdb) list
120 cmp %RDX_LP, %RCX_LP
121 jb HIDDEN_JUMPTARGET (__chk_fail)
122 END_CHK (MEMSET_CHK_SYMBOL (__memset_chk, unaligned))
123 #endif
124
125 ENTRY (MEMSET_SYMBOL (__memset, unaligned))
126 MEMSET_VDUP_TO_VEC0_AND_SET_RETURN (%esi, %rdi)
127 # ifdef __ILP32__
128 /* Clear the upper 32 bits. */
129 mov %edx, %edx
(gdb) print $rdi
$1 = 140737353858200
(gdb) print $rdx
$2 = 36
(gdb) print $esi
$3 = 0
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-08 12:26 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 [this message]
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
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-FbXT8SUm3H@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).