From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 474E6385842A; Mon, 2 Oct 2023 22:58:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 474E6385842A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1696287531; bh=/Gs1brN45IoFn5oQBugbeEhUtuz+IszuqCVQjz12LNE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=g2qkZ81G4i9jGYHh/0nT2VBYI/RcKjvCg3jxHAw+6WoRoBmzaflz+KpiL17Z5VW2s 5E9+gEht2ncb6jYY73lfmGLn43S4BbRV19n3KxtK3SAcoRM6LpkWDhOBMa8ccGRQZP I2F+cvkHMdplWBmaGRJhAPf3uF6TlYCbZW1rcs2M= From: "aburgess at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/30935] Regression exposed by new gdb.python/py-progspace-events.exp test and native-extended-gdbserver board Date: Mon, 02 Oct 2023 22:58:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: aburgess at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 14.1 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30935 --- Comment #1 from Andrew Burgess --- Bisected the problem back to commit: commit a2827364e2bf19910fa5a54364a594a5ba3033b8 Author: Andrew Burgess Date: Fri Sep 8 15:48:16 2023 +0100 gdb: remove final user of the executable_changed observer which is also one of mine. That commit changed when the auxv cache was cleared, so my guess is we're discarding the data when we previous weren't, which is why GDB is now trying to re-read the data, which is leading to the crash we see. I'll continue to dig into this and get a fix out asap. --=20 You are receiving this mail because: You are on the CC list for the bug.=