From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 77DA13857BAD; Mon, 11 Jul 2022 08:23:43 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 77DA13857BAD
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:23:43 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: string
X-Bugzilla-Version: 2.35
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: werner at suse dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29327-131-d6PYcgMO2m@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29327-131@http.sourceware.org/bugzilla/>
References: <bug-29327-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: glibc-bugs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Glibc-bugs mailing list <glibc-bugs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/glibc-bugs/>
List-Help: <mailto:glibc-bugs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jul 2022 08:23:43 -0000

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

--- Comment #14 from Dr. Werner Fink <werner at suse dot de> ---
(In reply to Noah Goldstein from comment #12)
> (In reply to Dr. Werner Fink from comment #9)

> >  (gdb) print $rdi
> >  $1 =3D 140737353858200
> >  (gdb) print $rdx
> >  $2 =3D 36
> >  (gdb) print $esi
> >  $3 =3D 0
>=20
> I don't see how those values could segfault,
>=20
> Are you sure `rdi` points to valid memory?

No I'm not, I only want to debug the memory usage of kodi with the help of
libmemusage.so and run into this problem.  Meanwhile I've tried the heaptra=
ck
tool to debug the memory usage of kodi (https://userbase.kde.org/Heaptrack).
This tool is also preloading a library libheaptrack_preload.so or
libheaptrack_inject.so.

As you can see at=20=20=20=20=20=20=20

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

there is also a different crash with memusage script but with dolphin with a
fully different stack.

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