-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On tour with r2 and sigbus :) #902
Comments
it would be great if you could show some more feedback in your crashes, because reproducing them implies fuzzing command execution which can result in rm -rf / and i’m too lazy to be careful. Please, provide ‘list’ of the 3 last items in the backtrace, then use ‘print ’ to identify the root cause of the crash. This is. a null deref, the length of the memcpy, the buffer of the command executed. etc Also, it would be great if you could also provide non-fuzz-based reproducible crashes or the patch itself :) On 08 May 2014, at 23:44, zonkzonk notifications@github.com wrote:
|
Im very sorry, that you are "too lazy to be careful". Why not setup a dedicated Linux VM? On the last point: How about creating an automated fuzz environment to check from time to I try to provide patch, if I can. |
can't reproduce in 0ecb57d |
morrn,
IN:
where buf.core is base64-encoded attached.
OUT:
r2 version: 773b033
greetings
z.
The text was updated successfully, but these errors were encountered: