aboutsummaryrefslogtreecommitdiff
path: root/gdb/NEWS
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2021-11-26 13:51:36 +0000
committerAndrew Burgess <aburgess@redhat.com>2022-01-12 11:19:48 +0000
commit393707788800b05448201fbb184ba758e26960fd (patch)
tree678f039f2aa09dc16899e259c3530bfe6044a5aa /gdb/NEWS
parent8864ef428d92e58b48ec11136d3b91622345c838 (diff)
downloadgdb-393707788800b05448201fbb184ba758e26960fd.zip
gdb-393707788800b05448201fbb184ba758e26960fd.tar.gz
gdb-393707788800b05448201fbb184ba758e26960fd.tar.bz2
gdb: new 'maint flush source-cache' command
This commit adds a new 'maint flush source-cache' command, this flushes the cache of source file contents. After flushing GDB is forced to reread source files the next time any source lines are to be displayed. I've added a test for this new feature. The test is a little weird, in that it modifies a source file after compilation, and makes use of the cache flush so that the changes show up when listing the source file. I'm not sure when such a situation would ever crop up in real life, but maybe we can imagine such cases. In reality, this command is useful for testing the syntax highlighting within GDB, we can adjust the syntax highlighting settings, flush the cache, and then get the file contents re-highlighted using the new settings.
Diffstat (limited to 'gdb/NEWS')
-rw-r--r--gdb/NEWS3
1 files changed, 3 insertions, 0 deletions
diff --git a/gdb/NEWS b/gdb/NEWS
index ad80e92..73eb022 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -70,6 +70,9 @@ show debug linux-nat
debug lin-lwp' respectively. Turning this setting on prints debug
messages relating to GDB's handling of native Linux inferiors.
+maint flush source-cache
+ Flush the contents of the source code cache.
+
* Changed commands
maint packet