-
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
EVAL is not reentrant #6131
Comments
From j.david.lowe@apple.comOn my system, this short program crashes within a few seconds of starting: ``` use v6.c; sub MAIN { The three failures I've observed are: More information: $ perl6 --version $ uname -a |
From @nwc10Thanks for the bug report. On Tue, Mar 07, 2017 at 05:12:34PM -0800, J . David Lowe wrote:
ASAN says: ==8139==ERROR: AddressSanitizer: attempting double-free on 0x6020008ef610 in thread T1: 0x6020008ef610 is located 0 bytes inside of 16-byte region [0x6020008ef610,0x6020008ef620) previously allocated by thread T1 here: Thread T1 created by T0 here: Thread T2 created by T0 here: SUMMARY: AddressSanitizer: double-free ../../.././libsanitizer/asan/asan_malloc_linux.cc:93 __interceptor_realloc Nicholas Clark |
The RT System itself - Status changed from 'new' to 'open' |
From @jnthnOn Wed, 08 Mar 2017 04:00:18 -0800, nicholas wrote:
Turned out to be a data race in producing (supposedly unique) serialization context IDs, meaning that some of the compilations were doomed to share state that should not be shared. Fixed the race, and added a test case in integration/eval-and-threads.t based on the code in this ticket. Thanks, /jnthn |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#130951 (status was 'resolved')
Searchable as RT130951$
The text was updated successfully, but these errors were encountered: