| 2021-10-18 16:30:57 |
Valeriy Fedotov |
description |
Hi!
I usually develop my code with (declaim (optimize debug)) for simpler debugging, and I noticed that coverage data gathered with sb-cover module changes a lot when I use this declaim.
Vanilla coverage data without any additional declaims to (declaim (optimize sb-cover:store-coverage-data)) does not highlight defvar, defpackage and many other forms.
But when debug is turned on I can get defvar, defpackage and other forms withous function body to be green or red. I do not know what is the mechanism behind marking them red or green. In my code they are always red, but my project is too large for attaching it here. In minimized version all defvars and defpackages are always red.
I'm attaching .zip archive with minimized version. You can launch it with
sbcl --script main.lisp
Also for convenience I attach image with non-debug-optimized result on the left side, and optimized on the right.
Thank you. |
Hi!
I usually develop my code with (declaim (optimize debug)) for simpler debugging, and I noticed that coverage data gathered with sb-cover module changes a lot when I use this declaim.
Vanilla coverage data without any additional declaims to (declaim (optimize sb-cover:store-coverage-data)) does not highlight defvar, defpackage and many other forms.
But when debug is turned on I can get defvar, defpackage and other forms withous function body to be green or red. I do not know what is the mechanism behind marking them red or green. In my code they are always red, but my project is too large for attaching it here. In minimized version all defvars and defpackages are always green.
I'm attaching .zip archive with minimized version. You can launch it with
sbcl --script main.lisp
Also for convenience I attach image with non-debug-optimized result on the left side, and optimized on the right.
Thank you. |
|
