Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
db424c0c
Commit
db424c0c
authored
Sep 13, 2017
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document the addition of debug:vmod_so_keep to 5.2.
parent
d1ac4b26
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
0 deletions
+8
-0
upgrading-5.2.rst
doc/sphinx/whats-new/upgrading-5.2.rst
+8
-0
No files found.
doc/sphinx/whats-new/upgrading-5.2.rst
View file @
db424c0c
...
...
@@ -21,6 +21,9 @@ We have updated the documentation for :ref:`ref_param_send_timeout`,
:ref:`ref_param_idle_send_timeout`, :ref:`ref_param_timeout_idle` and
:ref:`ref_param_ban_cutoff`.
Added the debug bit ``vmod_so_keep``, see :ref:`ref_param_debug` and
the notes about changes for developers below.
Changes to VCL
==============
...
...
@@ -137,6 +140,11 @@ Other changes
development of client apps, is now publicly available, see
:ref:`whatsnew_vut_5.2`.
* The debug bit ``vmod_so_keep`` instructs Varnish not to clean
up its copies of VMOD shared objects when it stops. This makes
it possible for VMOD authors to load their code into a debugger
after a varnishd crash. See :ref:`ref_param_debug`.
* *XXX: anything else, such as sanitizer flags?*
* *XXX: ...*
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment