0d999a6ef0
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.
|
||
|---|---|---|
| .. | ||
| cli-cmds.c | ||
| cli-cmds.h | ||
| cli-decode.c | ||
| cli-decode.h | ||
| cli-dump.c | ||
| cli-interp.c | ||
| cli-interp.h | ||
| cli-logging.c | ||
| cli-script.c | ||
| cli-script.h | ||
| cli-setshow.c | ||
| cli-setshow.h | ||
| cli-utils.c | ||
| cli-utils.h | ||