summaryrefslogtreecommitdiffstats
path: root/Help/release/3.10.rst
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2017-12-06 16:23:58 (GMT)
committerBrad King <brad.king@kitware.com>2017-12-06 16:39:03 (GMT)
commit8b2736c71ca6eb8e62a69f57ad07e4e19a95c936 (patch)
treedf7d3ab1300b235da99e0870efaaefe8c487e567 /Help/release/3.10.rst
parent7746fdb2fe0177341aadeafec2ae73aa08ddfaf6 (diff)
downloadCMake-8b2736c71ca6eb8e62a69f57ad07e4e19a95c936.zip
CMake-8b2736c71ca6eb8e62a69f57ad07e4e19a95c936.tar.gz
CMake-8b2736c71ca6eb8e62a69f57ad07e4e19a95c936.tar.bz2
server: Revert "Report backtraces in codemodel response"
The backtrace information is very repetitive and hugely increases the size of the codemodel object. We need to remove it until an alternative representation can be developed. Revert commit v3.10.0-rc1~393^2 (server: Report backtraces in codemodel response, 2017-06-20), except for the protocol version number (because it indicates other new things). Unfortunately this is incompatible with clients that expect the "crossReferences" field in targets. However, the regression in memory usage is quite serious, especially on large projects, and therefore breaks even older clients that do not use backtraces. Since the "crossReferences" field was only provided by one release (3.10.0), it is simplest to revert it outright for 3.10.1. Fixes: #17502
Diffstat (limited to 'Help/release/3.10.rst')
-rw-r--r--Help/release/3.10.rst12
1 files changed, 12 insertions, 0 deletions
diff --git a/Help/release/3.10.rst b/Help/release/3.10.rst
index 35fe602..6a19dbf 100644
--- a/Help/release/3.10.rst
+++ b/Help/release/3.10.rst
@@ -255,3 +255,15 @@ Other Changes
incompatible with the old behavior, it is expected that behavior
under typical use cases with properly-quoted command-lines has
not changed.
+
+Updates
+=======
+
+Changes made since CMake 3.10.0 include the following.
+
+3.10.1
+------
+
+* The :manual:`cmake-server(7)` ``codemodel`` response ``crossReferences``
+ field added by 3.10.0 has been dropped due to excessive memory usage.
+ Another approach will be needed to provide backtrace information.