Commit f1a6a35
committed
fuzz: check the method call return code as well
I'm actually baffled how I managed to miss this, but thanks to sheer
luck the crashes were getting detected, albeit a bit later (when dfuzzer
detected the remote PID disappeared). All this surfaced once I was
trying to dump a reproducer for each specific fail/crash, and was
getting wrong values (i.e. values from a couple of iterations later).
tl;dr we ignored when the method returned no reply or timed out.1 parent 4930c31 commit f1a6a35
1 file changed
Lines changed: 6 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
482 | 482 | | |
483 | 483 | | |
484 | 484 | | |
| 485 | + | |
| 486 | + | |
| 487 | + | |
| 488 | + | |
| 489 | + | |
| 490 | + | |
485 | 491 | | |
486 | 492 | | |
487 | 493 | | |
| |||
0 commit comments