Whoops, accidentally pressed the send button. Here is the information: Errors that I get: *** Error in `/home/alex/git/rakudobrew/moar-nom/install/bin/moar': double free or corruption (!prev): 0x0eab14f8 *** or *** Error in `/home/alex/git/rakudobrew/moar-nom/install/bin/moar': free(): invalid pointer: 0x09b99c58 *** or similar
Valgrind output: https://gist.github.com/AlexDaniel/a3ce0f8315ddd93fed38 The whole code: https://gist.github.com/AlexDaniel/76569d745033eac7e3b3 Please note that I cannot golf it down to anything shorter, any change to the code makes the problem disappear. It is very unstable. I was quickly writing that code to get my stuff done when I suddenly stumbled upon that problem. If you change the input file it will stop breaking as well. Exact instructions to run it: * Run it like this: ./asc-to-svg pins.ASC B * please note argument B, it is important * Here is the file pins.ASC https://files.progarm.org/pins.ASC * Here is how the output looks like: https://gist.github.com/AlexDaniel/76569d745033eac7e3b3 * Sometimes it works correctly, but most of the times it breaks * On my machine it takes 36 seconds to break * If it didn't break after 36 seconds, then it will not break * It breaks on exactly the same line every time (at least that's what I'm seeing right now) * It depends on the code a lot. For example, if you remove this unused line: my $FILENAME = 'pins.ASC'; it will stop breaking 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-follo...@perl.org > wrote: > Greetings, > > This message has been automatically generated in response to the > creation of a trouble ticket regarding: > "double free or corruption, invalid pointer", > a summary of which appears below. > > There is no need to reply to this message right now. Your ticket has been > assigned an ID of [perl #125500]. > > Please include the string: > > [perl #125500] > > in the subject line of all future correspondence about this issue. To do > so, > you may reply to this message. > > Thank you, > perl6-bugs-follo...@perl.org > > ------------------------------------------------------------------------- > For any missing information see IRC log: > http://irclog.perlgeek.de/perl6/2015-06-28#i_10815783 > >
