aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.python/py-section-script.py
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2023-11-13 09:31:20 +0100
committerTom de Vries <tdevries@suse.de>2023-11-13 09:31:20 +0100
commit6b682bbf86f37982ce1d270fb47f363413490bda (patch)
tree10141f97016d2c71c46df045162f597ffefef1e8 /gdb/testsuite/gdb.python/py-section-script.py
parentaba9fa5f4be8c27e07c5330957fff17e4160920b (diff)
downloadbinutils-6b682bbf86f37982ce1d270fb47f363413490bda.zip
binutils-6b682bbf86f37982ce1d270fb47f363413490bda.tar.gz
binutils-6b682bbf86f37982ce1d270fb47f363413490bda.tar.bz2
[gdb/tui] Fix Wmaybe-uninitialized in tui_find_disassembly_address
When building gdb with -O2, we run into: ... gdb/tui/tui-disasm.c: In function ‘CORE_ADDR tui_find_disassembly_address \ (gdbarch*, CORE_ADDR, int)’: gdb/tui/tui-disasm.c:293:7: warning: ‘last_addr’ may be used uninitialized \ in this function [-Wmaybe-uninitialized] if (last_addr < pc) ^~ ... The warning triggers since commit 72535eb14bd ("[gdb/tui] Fix segfault in tui_find_disassembly_address"). Fix the warning by ensuring that last_addr is initialized at the point of use: ... + last_addr = asm_lines.back ().addr; if (last_addr < pc) ... Tested on x86_64-linux.
Diffstat (limited to 'gdb/testsuite/gdb.python/py-section-script.py')
0 files changed, 0 insertions, 0 deletions