-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
cg (character device) issues #1938
Comments
found a different crash this time (64bit). we should not allow character devices for cg as workaround.
Greetings |
this crash exposes a random bug which cant be reproduced all the time. i This crash happens in a really wtf situation because op is -1, and all we can try to fuzz the assemblers, but assembling @U\245 doesnt crashes but if i run this with valgrind i always get the same output :/ so its On 01/10/2015 07:51 PM, zonkzonk wrote:
|
I thought, checking wat to return could be a good idea. I will save bufs from 19 static int assemble(RAsm *a, RAsmOp *op, const char *str) { |
I'm on linux_64, and am seeing this bug manifested in a few ways. |
I've gotten this particular crash a few times, working on a fix now
|
bunch of things changed since I last synced... still going to fix the issue with /dev/zero I saw |
wrong patch |
Theres nothing wrong in opening a device. Its also a file
|
morrn,
cg [path] where path is /dev/urandom, with 32 bit:
however since last commit, I could not reproduce(*) with
while :; do sleep 0.1 && r2 -qc 'cg /dev/urandom' /bin/ls; done.
wat do ? :)
Greetings
--zlul
ofc, I can provide core file in private
The text was updated successfully, but these errors were encountered: