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: Thu, 14 Jul 2022 07:36:26 +0000 [thread overview]
Message-ID: <bug-29327-131-sY1l3AGm3Y@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 #24 from Dr. Werner Fink <werner at suse dot de> ---
Created attachment 14209
--> https://sourceware.org/bugzilla/attachment.cgi?id=14209&action=edit
dumpctl.log
(In reply to Noah Goldstein from comment #23)
> (In reply to H.J. Lu from comment #22)
> > (In reply to Dr. Werner Fink from comment #21)
> > > (In reply to H.J. Lu from comment #20)
> > > > (In reply to Dr. Werner Fink from comment #16)
> > > > > Created attachment 14205 [details]
> > > > > audit.log
> > >
> > > [...]
> > >
> > > >
> > > > We need the audit.log from crash.
> > >
> > > Yes ... this should be
> > > https://sourceware.org/bugzilla/attachment.cgi?id=14205
> >
> > But your command was
> >
> > /kodi> ( setenv LD_AUDIT ./auditmod.so ; /usr/lib64/kodi/kodi.bin ) | & tee
> > audit.log
> >
> > and it didn't crash.
>
> Likewise for:
> pltenter: memset: dst=0x7ff43008ed78, src=0, len=8
>
> I don't see this would segfault if `dst` has write permissions.
If I try both
LD_AUDIT=${PWD}/auditmod.so LD_PRELOAD=/lib64/libmemusage.so
it simply crashes with a SIGSEGV
werner@noether:/usr/src/werner/auditmod> LD_AUDIT=${PWD}/auditmod.so
LD_PRELOAD=/lib64/libmemusage.so /usr/lib64/kodi/kodi.bin
version: 2
Segmentation fault (core dumped)
no output from auditmod.so ... only a core dump
werner@noether:/usr/src/werner/auditmod> sudo coredumpctl | tail -n 1
Thu 2022-07-14 09:30:28 CEST 16275 223 50 SIGSEGV present
/usr/lib64/kodi/kodi.bin
werner@noether:/usr/src/werner/auditmod> sudo coredumpctl dump 16275 -o
/tmp/core > dumpctl.log 2>&1
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-14 7:36 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
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 [this message]
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-sY1l3AGm3Y@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).