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
failed assertion in optimizer.c:945 #1236
Comments
parrot_old works fine, correctly erroring with 'Divide by zero'. because the pc (address) of the returned exception handler is something different. |
When an op throws an exception like div by zero, eval just returns the address of the handler, not the handler. So we only know that something is wrong, not what. The exception message should be improved later. For now just error with eval_ins: unhandled exception for op '%s' Fixes #1236
When an op throws an exception like div by zero, eval just returns the address of the handler, not the handler. So we only know that something is wrong, not what. The exception message should be improved later. For now just error with eval_ins: unhandled exception for op '%s' Fixes #1236
When an op with only constants args throws an exception like div by zero, eval just returns the address of the handler, not the handler. So we only know that something is wrong, not what. The exception message should be improved later. For now just error with eval_ins: unhandled exception for op '%s' Fixes #1236
When an op with only constants args throws an exception like div by zero, eval just returns the address of the handler, not the handler. So we only know that something is wrong, not what. The exception message should be improved later. For now just error with eval_ins: unhandled exception for op '%s' Fixes #1236
Hello, I was using American Fuzzy Lop (afl-fuzz) to fuzz input to the
parrot
program on Linux and I found a failed assertion when using this program as input:The file can be executed as
./parrot filename
to cause a failed assertion and segmentation fault.gdb backtrace from the resultant core file:
Let me know if I can provide any more information to help narrow down this issue.
The text was updated successfully, but these errors were encountered: