From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 04F17395443B; Fri, 6 May 2022 13:05:16 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 04F17395443B From: "craig.blackmore at embecosm dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/29124] New: Regressions in overlays.exp Date: Fri, 06 May 2022 13:05:16 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: craig.blackmore at embecosm dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2022 13:05:17 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D29124 Bug ID: 29124 Summary: Regressions in overlays.exp Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: craig.blackmore at embecosm dot com Target Milestone: --- overlays.exp is only tested on m32r. Until recently I was getting 81 passes testing on the builtin m32r sim, however, there are 14 unexpected failures = with latest master commit 0ee8858e7aeca5ba5f702204daad2ddd290ef229. Using git bisect, I found that the regressions appeared when the new DWARF indexer was enabled in commit 3d20b8d99a54382e6e1a6c433e71e0775c6856c6. Loo= king at the regressions, there seems to be an issue with symbol lookup, but I ha= ve not tracked down the root cause. Below is a summary of the failures. The first few regressions are for `print ` commands that end up printing the wrong symbol: print foo $1 =3D {int (int)} 0x400000 <*foo*> (gdb) PASS: gdb.base/overlays.exp: get foo load address print bar $2 =3D {int (int)} 0x400024 <*foo*> (gdb) FAIL: gdb.base/overlays.exp: get bar load address print baz $3 =3D {int (int)} 0x400048 <*baz*> (gdb) PASS: gdb.base/overlays.exp: get baz load address print grbx $4 =3D {int (int)} 0x40006c <*baz*> (gdb) FAIL: gdb.base/overlays.exp: get grbx load address ... print bar $10 =3D {int (int)} 0x300000 (gdb) FAIL: gdb.base/overlays.exp: get bar runtime address ... print grbx $12 =3D {int (int)} 0x380000 (gdb) FAIL: gdb.base/overlays.exp: get grbx runtime address Next, the test fails to find addresses for the same symbols as above (which= is done using print ): print 0x400000 !=3D 0x300000 $17 =3D 1 (gdb) PASS: gdb.base/overlays.exp: foo's LMA !=3D VMA print 0 !=3D 0 $18 =3D 0 (gdb) FAIL: gdb.base/overlays.exp: bar's LMA !=3D VMA print 0x400048 !=3D 0x380000 $19 =3D 1 (gdb) PASS: gdb.base/overlays.exp: baz's LMA !=3D VMA print 0 !=3D 0 $20 =3D 0 (gdb) FAIL: gdb.base/overlays.exp: grbx's LMA !=3D VMA Then, for the same symbols, GDB sets breakpoints on the wrong symbol: break foo Breakpoint 2 at 0x300008: file binutils-gdb/gdb/testsuite/gdb.base/foo.c, l= ine 5. (gdb) PASS: gdb.base/overlays.exp: break foo break bar Note: breakpoint 2 also set at pc 0x300008. Breakpoint 3 at 0x300008: file binutils-gdb/gdb/testsuite/gdb.base/foo.c, l= ine 5. (gdb) FAIL: gdb.base/overlays.exp: break bar break baz Breakpoint 4 at 0x380008: file binutils-gdb/gdb/testsuite/gdb.base/baz.c, l= ine 5. (gdb) PASS: gdb.base/overlays.exp: break baz break grbx Note: breakpoint 4 also set at pc 0x380008. Breakpoint 5 at 0x380008: file binutils-gdb/gdb/testsuite/gdb.base/baz.c, l= ine 5. (gdb) FAIL: gdb.base/overlays.exp: break grbx The remaining 6 failures are due to failing to hit the above breakpoints in= the expected place and produce the expected backtrace. --=20 You are receiving this mail because: You are on the CC list for the bug.=