[Bug gdb/30318] New: GDB showing outdate value even though DWARF has a new value.

[Bug gdb/30318] New: GDB showing outdate value even though DWARF has a new value.

[hluaw at connect dot ust.hk]

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

            Bug ID: 30318
           Summary: GDB showing outdate value even though DWARF has a new
                    value.
           Product: gdb
           Version: 13.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: hluaw at connect dot ust.hk
  Target Milestone: ---

Given the following code:
#include "stdint.h"
int a, b;
int func_17() {
  int32_t *l_26 = 0;
  int32_t **c = &l_26;
  *c = &a;
  b = 0;
  return a;
}
int main() { func_17(); }

Compiled with gcc 12.2.0 with -O2 and -g

For l_26 the DWARF says:
(gdb) info addr l_26
Symbol "l_26" is multi-location:
  Base address 0x401020  Range 0x401020-0x401020: the constant 0
  Range 0x401020-0x40102a: a complex DWARF expression:
     0: DW_OP_addr 0x404030
     9: DW_OP_stack_value
(gdb) p $pc
$2 = (void (*)()) 0x401020 <main>
(gdb) p l_26
$3 = (int32_t *) 0x0

Though $pc is at the inclusive beginning of a valid range, gdb still says it's
zero.

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

[Bug gdb/30318] GDB showing outdate value even though DWARF has a new value.

[hluaw at connect dot ust.hk]

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

LU Hongyi <hluaw at connect dot ust.hk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #1 from LU Hongyi <hluaw at connect dot ust.hk> ---
It seems the same issue as 28987, sorry for the duplicate.

*** This bug has been marked as a duplicate of bug 28987 ***

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