DOC: Add information about leak checking and valgrind #17934
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
seberg
force-pushed
the
add-advanced-tools-docs
branch
from
7d696c9
to
4a08496
Compare
|
Hmm, ok this is not the right place, and I didn't realize we actually have a GDB primer: https://17314-908607-gh.circle-artifacts.com/0/doc/build/html/dev/development_environment.html#debugging |
seberg
force-pushed
the
add-advanced-tools-docs
branch
2 times, most recently
from
9505f9f
to
490bf5b
Compare
This is not meant to be a fool-proof guide. It isn't and I do not want to expect people to use it... But I realize that I use these things semi-regulary (even if I never bother to remove all wrinkles) and it is good to have the information somewhere so that everyone knows where to look.
seberg
force-pushed
the
add-advanced-tools-docs
branch
from
490bf5b
to
bfceca9
Compare
|
OK, just renamed it slightly and added a reference back to the earlier "Debugging" section, so lets see what you think whether this is the right place/scope or not. |
mattip
reviewed
Dec 5, 2020
| errors on its own. An additional advantage of a debug build of Python is that | ||
| it allows detecting memory leaks. | ||
|
|
||
| A tool to make this easier is `pytest-leaks <https://github.com/abalkin/pytest-leaks>`_, |
There was a problem hiding this comment.
Maybe move the URL to the end of the section or so?
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
Thanks @seberg |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is not meant to be a fool-proof guide. It isn't and I
do not want to expect people to use it...
But I realize that I use these things semi-regulary (even if I
never bother to remove all wrinkles) and it is good to have the
information somewhere so that everyone knows where to look.
I am not sure I want to smoothen out this much more, there are wrinkles in these tools, there are things that could be figured out/improved that I never bothered to do. I would hope that someone feels like adding that GDB quickstart before these things, but I don't use gdb with breakpoints etc. that often myself (and if usually from the IDE, which may require trickier setup that I am happy to show about, but do not feel like squeezing into docs on the website).