darlinghq/darling-gdb
1
0
Fork 0
mirror of https://github.com/darlinghq/darling-gdb.git synced 2025-02-26 04:15:28 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

* gdb.texinfo (Caching Data of Remote Targets): Add note on

Browse Source 
non-stop mode's affect on remote caching.
This commit is contained in:
Doug Evans 2009-09-01 18:48:58 +00:00
parent 44453f85d9
commit 29b090c057
2 changed files with 13 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/doc/ChangeLog
View File

@ -1,3 +1,8 @@
2009-09-01 Doug Evans <dje@google.com>
* gdb.texinfo (Caching Data of Remote Targets): Add note on
non-stop mode's affect on remote caching.
2009-08-31 Jacob Potter <jdpotter@google.com>
Doug Evans <dje@google.com>

10
gdb/doc/gdb.texinfo
View File

@ -8427,8 +8427,14 @@ performance, because it reduces the overhead of the remote protocol by
bundling memory reads and writes into large chunks. Unfortunately, simply
caching everything would lead to incorrect results, since @value{GDBN}
does not necessarily know anything about volatile values, memory-mapped I/O
addresses, etc. Therefore, by default, @value{GDBN} only caches data
known to be on the stack. Other regions of memory can be explicitly marked
addresses, etc. Furthermore, in non-stop mode (@pxref{Non-Stop Mode})
memory can be changed @emph{while} a gdb command is executing.
Therefore, by default, @value{GDBN} only caches data
known to be on the stack@footnote{In non-stop mode, it is moderately
rare for a running thread to modify the stack of a stopped thread
in a way that would interfere with a backtrace, and caching of
stack reads provides a significant speed up of remote backtraces.}.
Other regions of memory can be explicitly marked as
cacheable; see @pxref{Memory Region Attributes}.
@table @code