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
Parrot segfaults after subtype type check fails #218
Comments
From @masakr30087: I was not able to produce a failing type check of any kind without |
From @chromaticOn Thursday 07 August 2008 05:16:40 Carl Mäsak wrote:
It's not really a segfault, but libc sending SIGABRT on a dodgy memory free: Program received signal SIGABRT, Aborted. The relevant code is: /* clear freed contexts */ ... and slot is 8. I don't know how many links in the list it has gone I'll keep digging, unless someone else beats me to it first. (The rest of the backtrace is amusing. It appears that an exception handler -- c |
The RT System itself - Status changed from 'new' to 'open' |
From @masakThis works now. |
@masak - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#57710 (status was 'resolved')
Searchable as RT57710$
The text was updated successfully, but these errors were encountered: