From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 68586385B534; Fri, 10 Feb 2023 09:33:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 68586385B534 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1676021631; bh=7PEB33EGRiO7U3KHDLD9cb32o2U0LvqbWlg6YMA65xw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=X1QhMmq+BOnKF9c3Wc8LXTlGDUgnyeb++E0nsHn8P/H3IojwthmmCfVl14yTQeycT zwK/H3GG1BXJzA13/RiPdTVPrGAYjmCJ1qOlCQ3sgrhNtZ29SWPXaauUFaPFOQk0yf 2+2rY1EbgC+Cj9xLhCTJF8FUKNvSOaL9ewXaH65c= From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/30106] backtrace overwrites other memory Date: Fri, 10 Feb 2023 09:33:49 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.36 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fweimer at redhat dot com 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: everconfirmed cc cf_reconfirmed_on bug_status 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30106 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 CC| |fweimer at redhat dot com Last reconfirmed| |2023-02-10 Status|UNCONFIRMED |WAITING --- Comment #1 from Florian Weimer --- Please provide a smaller reproducer. It's also not clear how you have set up your 32-bit build environment. You can also set a hardware watchpoint using GDB and get a backtrace at the point the variable is overwritten. --=20 You are receiving this mail because: You are on the CC list for the bug.=