From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6C6A53858282; Mon, 25 Jul 2022 06:00:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6C6A53858282 From: "werner at suse dot de" To: glibc-bugs@sourceware.org Subject: [Bug string/29327] A SIGSEGV in hardware optimized memset for sse2 __memset_sse2_unaligned_erms() Date: Mon, 25 Jul 2022 06:00:52 +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: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2022 06:00:53 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D29327 --- Comment #31 from Dr. Werner Fink --- (In reply to Noah Goldstein from comment #30) > (In reply to Dr. Werner Fink from comment #lib29) > > Maybe it is a combination of preloading libmemusage.so with a program u= sing > > the libsqlite3.so.0 as 68701503120 bytes seems to be very large for the > > address 0x2db2320 as well as this address seems not be (m)allocated bef= ore > > as the addresses before > Is there a reason to think this is a bug with memset and not invalid > parameters? If this is a bug with memset ... I don't know. What I know is that the bug happens if libmemusage.so is preloaded. And I'm not the only one, see https://bugzilla.opensuse.org/show_bug.cgi?id=3D1201047#c14 interestingly if I use heaptrack (https://userbase.kde.org/Heaptrack) this crash does not happen. Also various valgrind tools do not trigger such a crash. --=20 You are receiving this mail because: You are on the CC list for the bug.=