-
Notifications
You must be signed in to change notification settings - Fork 1
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
native 2d array example SEGV's #5873
Comments
From @dogbert17# the system, 32 bit Linux vm running under VirtualBox dogbert@dogbert-VirtualBox ~ $ perl6 -v # the problem AlexDaniel did a quick bisect with the bisectbot and uncovered the following /dogbert17 |
From @cokeAttaching gistfile to ticket -- |
From @cokeuse v6; init-array(0, $size - 1, $size * $size); |
The RT System itself - Status changed from 'new' to 'open' |
From @lizmatConfirmed on macOS. Running with MVM_SPESH_DISABLE=1 does not prevent the segv. Running with —optimize=0 and —optimize=1 *does* prevent the issue. —optimize=2 and higher shows the problem. Running with “use trace” shows a *lot* of output: the last lines shown are: 12 (/Users/liz/Github/rakudo.moar/1 line 13) So it looks like evaluating $c does it? Feels like some kind of memory corruption to me.
|
From lucasbuchala@gmail.comHi. I narrowed the code to this snippet, I hope it helps. It segfault my int @a[1]; sub f($i) { @a[0]; print "$i "; if $i { f($i-1) } f(839); |
From @jnthnOn Wed, 07 Dec 2016 14:33:54 -0800, jan-olof.hendig@bredband.net wrote:
It managed to look like both a GC bug and an inlining bug in MoarVM, but actually ended up being a boring callstack region overflow bug that affected some (and only some) heavily recursive code. It's fixed now, and there's a test to cover it in integration/deep-recursion-initing-native-array.t. /jnthn |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#130294 (status was 'resolved')
Searchable as RT130294$
The text was updated successfully, but these errors were encountered: