mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2020-11-02 15:01:17 -04:00
commit 40679616ed
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
doc/todo/--debug-level___40__and__47__or_-c_annex.debug-level__41___+_more_debug_information_from_git-annex/comment_1_58e729e2fa58b28d247eeda579bb9329._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-11-02T18:48:44Z"
content="""
Every call to debugM does add overhead both in time to run it
(checking if debugging is enabled is nonzero overhead and this will add up
if it's done a few million times or whatever) and in time to write
a useful explanation.
It seems to me that debugging is best added when trying to debug something,
or when there's a readily available value that can be output (such as the
safety proof that is debugged when dropping, or external special remote
messages).
Trying to add enough useful debugging information to 60,000 lines of code
that any possible thing it might do will have a useful debug trace seems
like a recipe to end up with 100,000 lines of code. It would be easier to
run the code in a debugger and step through it at that point.
"""]]