aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc/ChangeLog
diff options
context:
space:
mode:
authorZhouyi Zhou <zhouzhouyi@gmail.com>2017-08-22 15:32:19 +0100
committerPedro Alves <palves@redhat.com>2017-08-22 15:32:19 +0100
commit0d999a6ef0f98b22430d70951408869864c979e0 (patch)
treed52c4e826f32083f59cb7675e34a0336e734d1ae /gdb/doc/ChangeLog
parent329d5e7e56f852dcf9956683be4345c165d277db (diff)
downloadgdb-0d999a6ef0f98b22430d70951408869864c979e0.zip
gdb-0d999a6ef0f98b22430d70951408869864c979e0.tar.gz
gdb-0d999a6ef0f98b22430d70951408869864c979e0.tar.bz2
List actual code around more than one location
With the following C++ code: int bar() { return 0;} int bar(int) { return 0; } GDB behaves as: (gdb) list bar file: "overload.cc", line number: 1 file: "overload.cc", line number: 2 It would be better for GDB to list the actual code around those two locations, not just print the location. Like: (gdb) list bar file: "overload.cc", line number: 1 1 int bar() { return 0;} 2 int bar(int) { return 0; } file: "overload.cc", line number: 2 1 int bar() { return 0;} 2 int bar(int) { return 0; } That's what this this commit implements. Tested on x86-64 GNU/Linux. gdb/ChangeLog: 2017-08-22 Zhouyi Zhou <zhouzhouyi@gmail.com> * cli-cmds.c (list_commands): List actual code around more than one location.
Diffstat (limited to 'gdb/doc/ChangeLog')
0 files changed, 0 insertions, 0 deletions