freenode/#sbcl - IRC Chatlog
Search
10:51:05
pfdietz
I've wanted to be able to compile sbcl with coverage, so I could see what parts are not being tested. Also, random test generation + coverage => automatically generating minimized tests that extend coverage.
12:00:48
pkhuong
pfdietz: the easiest way to get coverage everywhere might be editcore + HW/binary tracing like honggfuzz?
12:02:14
pfdietz
I want something where the coverage is made available in a form the reducer can easily access. It would also help if the a snapshot of the coverage could be taken and the state rolled back to the snapshot.
12:03:08
pfdietz
So: generate a test case, determine that it extends coverage, then reduce it to a minimal form that still extends coverage (and repeat that if the original had more coverage than the reduced form).
12:03:52
pfdietz
This is inspired right now by Doug K's comment on vop coverage in the most recent commit.
12:08:28
pkhuong
i don't have access to any machine with intel pt, but I do have BTS. i'll try to hack something up with intel's PMU today
12:28:00
pkhuong
the hardest part will be dropping branches to / from the C runtime and newly generated code
12:31:42
pfdietz
The approach I've taken on this sort of thing is instrumenting lisp when it's compiled. So if I can recompile part of the compiler, I can collect the information I want.