diff options
| author | Pedro Alves <palves@redhat.com> | 2013-09-05 14:49:13 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2013-09-05 14:49:13 +0000 |
| commit | 7c33b57c1551d8a15edbad6e5da5aab1b05e6ab0 (patch) | |
| tree | da7d047f84c3fbc27a1c538a8a399f5d18a8853a /config.guess | |
| parent | 9f8edbd5635f05ca5682796e4e34d7ce19549d5d (diff) | |
| download | gdb-7c33b57c1551d8a15edbad6e5da5aab1b05e6ab0.zip gdb-7c33b57c1551d8a15edbad6e5da5aab1b05e6ab0.tar.gz gdb-7c33b57c1551d8a15edbad6e5da5aab1b05e6ab0.tar.bz2 | |
dwarf2loc.c: minor cleanup. don't print integer with paddress.
A couple years ago, dwarf_expr_fetch used to return a CORE_ADDR. It
was made to return a ULONGEST since, and the 'dwarf_regnum' local
adjusted accordingly, but, we kept printing it with paddress.
gdbarch_dwarf2_reg_to_regnum takes the register number as 'int', so
there's really no point in using ULONGEST/pulongest either.
gdb/
2013-09-05 Pedro Alves <palves@redhat.com>
* dwarf2loc.c (dwarf2_evaluate_loc_desc_full): 'dwarf_regnum'
local is now int instead of ULONGEST. Print it with %d
instead of paddress.
Diffstat (limited to 'config.guess')
0 files changed, 0 insertions, 0 deletions