You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Fix some warnings from Sphinx
* Correct headings to avoid duplicate object description warning
* Add typedef and name to error codes matching style of PluginErrCodes
* Add correct directive
Copy file name to clipboardExpand all lines: doc/contributors_guide/tips_and_tricks.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -171,7 +171,7 @@ to rerun valgrind on that issue, you can run
171
171
172
172
Both of the above commands will write the output to `<BUILD_DIR>/Testing/Temporary/MemoryChecker.<#>.log`, where `<#>` is the test number.
173
173
174
-
```note
174
+
```{note}
175
175
The first time you run `make memcheck`, a supression file will be created, suppressing issues that does not comes from DLite.
176
176
Generating a suppression file may take long time, but it will only be generated once unless you manually add more suppressions to one of the `cmake/valgrind-*.supp` files.
0 commit comments