diff options
| author | Yao Qi <yao@codesourcery.com> | 2013-10-31 20:49:49 +0800 |
|---|---|---|
| committer | Yao Qi <yao@codesourcery.com> | 2013-11-20 11:40:55 +0800 |
| commit | b12039c63764299237a899c986be7a557aa62807 (patch) | |
| tree | b8a2d317705ae7b3729b2824c0b1e51055558adb /gdb/m2-valprint.c | |
| parent | 68c765e263432b1aa5f5a54edc358eba302be4ca (diff) | |
| download | gdb-b12039c63764299237a899c986be7a557aa62807.zip gdb-b12039c63764299237a899c986be7a557aa62807.tar.gz gdb-b12039c63764299237a899c986be7a557aa62807.tar.bz2 | |
Don't stress 'remote' in "Data Caching" in doc
When I try to describe the cache and its related commands (in a
cache-per-address-space world), I find hard to add, because
existing doc is focused on remote debugging, while data cache is used
regardless of the target. More precisely, GDB cache target data,
instead of remote data.
gdb/doc:
2013-11-20 Yao Qi <yao@codesourcery.com>
* gdb.texinfo (Data): Rename menu item.
(Caching Remote Data): Rename to ...
(Caching Target Data): ... it. Update.
Diffstat (limited to 'gdb/m2-valprint.c')
0 files changed, 0 insertions, 0 deletions