[Bug rust/31079] Rustc test not hitting bp as expected for 1.73 or greater versions

["tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
With git master, info locals shows both variables:

(gdb) info local _x
_x = 0
_x = 5

"_x = 0" is wrong but at the same time, gdb is just using
the location expression the compiler gave it.

I see rustc now emits lexical blocks to try to explain
the shadowing.  However, in this simple of a test case,
they end up all having the same range.

disassemble/s also shows the lines are reordered, even
with 'opt-level=0'.  Not sure what is up there, but often
these very simple tests aren't the best view into what
the compiler is doing.

FWIW normally if two different compilers exhibit different
behavior in the same version of gdb, that points to a compiler
issue.  gdb is normally at the mercy of the debuginfo that
the compiler creates.

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