| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Replace not just long sequences of digits in report titles, but every
sequence of '0'-'9' that is not surrounded by word characters.
As such matches will overlap and Go does not (currently?) support regexp
lookarounds, do the replacement multiple times until there is nothing
more to do. This should not slow down syzkaller, since this code is
only invoked during crash processing.
Restrict LINE replacement only to fragments that have a preceeding file
name. This prevents replacements like [1:2] -> [NUM:LINE].
|
| |
|
|
|
|
|
|
| |
The format of the panic message means that we get lots of duplicate
reports. Normalize KASAN report titles. In particular, strip the code
name since it encodes the size of the redzone, which may vary depending
on the test case, especially if the report is triggered by a false
positive.
|
| | |
|
| |
|
|
|
| |
These can fail in many functions, include the calling function in
the report
|
| | |
|
| | |
|
| |
|
|
|
|
| |
We already have a pattern to match "Fatal trap N: ..." panics, but the
format of our backtraces has changed since it was added. Add another
pattern which correctly matches a few instances generated by syzbot.
|
| |
|
|
|
| |
The plain panic message includes an absolute path to the source file
where we panicked, which may be too long for a report title.
|
|
|
linux_test.go is total mess and very hard to work with.
Turns out we had 2 tests that do exactly the same
(verify Report), but nobody ever noticed.
Move all test data to testdir/. One file per crash.
|