aboutsummaryrefslogtreecommitdiff
path: root/bfd
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@polymtl.ca>2020-07-14 23:18:01 -0400
committerSimon Marchi <simon.marchi@polymtl.ca>2020-07-14 23:18:30 -0400
commit054a0959265eb89210626b6f2d84b93b82ef7ae9 (patch)
tree59b62b08662c42c20e51e262fa327b987c4756a3 /bfd
parent360f1cd72da997ff5300db7ce76c8727db046868 (diff)
downloadgdb-054a0959265eb89210626b6f2d84b93b82ef7ae9.zip
gdb-054a0959265eb89210626b6f2d84b93b82ef7ae9.tar.gz
gdb-054a0959265eb89210626b6f2d84b93b82ef7ae9.tar.bz2
gdb/testsuite/lib/dwarf.exp: fix addr_size parameter comments
The comments modified in this patch claim that the addr_size parameters can take the value 32 or 64 (suggesting the value is in bits). In fact, the expected value is in bytes, either 4 or 8. The actual value in the DWARF info is in bytes. And we can see that the default values used (if addr_size == "default") are: if {$_cu_addr_size == "default"} { if {[is_64_target]} { set _cu_addr_size 8 } else { set _cu_addr_size 4 } } gdb/testsuite/ChangeLog: * lib/dwarf.exp (Dwarf::cu, Dwarf::tu, Dwarf::lines): Change valid values in documentation for addr_size to 4 and 8. Change-Id: I4a02dca2bb7992198864e545ef099f020f54ff2f
Diffstat (limited to 'bfd')
0 files changed, 0 insertions, 0 deletions