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
double free or corruption, invalid pointer #4356
Comments
From @AlexDanielFor any missing information see IRC log: |
From @AlexDanielWhoops, accidentally pressed the send button. Here is the information: Errors that I get: Valgrind output: The whole code: Exact instructions to run it: Linux Margo 3.16.0-4-586 #1 Debian 3.16.7-ckt4-3 (2015-02-03) i686 GNU/Linux JimmyZ thinks that it is a gc bug. On Sun, Jun 28, 2015 at 10:00 AM, perl6 via RT <perl6-bugs-followup@perl.org
|
From @AlexDanielWrong link. On Sun, Jun 28, 2015 at 10:00 AM, perl6 via RT <perl6-bugs-followup@perl.org
|
From @FROGGSMore backtrace: [...] Program received signal SIGABRT, Aborted. |
The RT System itself - Status changed from 'new' to 'open' |
From @MasterDuke17I ran this in a loop both in and outside valgrind for several hours and never got an error of any kind. I haven't attempted to golf or bisect it, but I believe whatever the problem was it's now fixed. |
From @AlexDanielOn 2017-02-26 20:16:14, ddgreen@gmail.com wrote:
That's not surprising given that the problem went away if you did *any* kind of change to the source code. Now that rakudo changed a lot, surely it doesn't crash anymore. Does it mean that the bug was fixed? Nobody knows. But I guess we should close this anyway. |
From @AlexDanielI'll close this ticket. I'm failing to reproduce the issue on 2015-ish versions of rakudo, let alone HEAD. I think the actual problem was resolved and hopefully there are tests for it, but trying to find what exactly fixed it is a total waste of time unfortunately. Even with all powers of whateverables this is not going to happen. Maybe I can try bisecting it manually, but I know that it will just point to a random moar/nqp bump and that will be it. We'd much rather spend time on new SEGV tickets than this one. On 2017-02-26 20:55:48, alex.jakimenko@gmail.com wrote:
|
@AlexDaniel - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#125500 (status was 'rejected')
Searchable as RT125500$
The text was updated successfully, but these errors were encountered: