-
-
Save timo/8f9a5591cdb48dcd0ab1 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ok 21 - Initial thread has an ID | |
| ok 22 - we didn't segfault | |
| ==4664== Thread 3: | |
| ==4664== Invalid read of size 4 | |
| ==4664== at 0x4F3CC0C: push_work_to_thread_in_tray (collect.c:390) | |
| ==4664== by 0x4F3D25F: process_worklist (collect.c:458) | |
| ==4664== by 0x4F3D59A: MVM_gc_collect (collect.c:87) | |
| ==4664== by 0x4F36E26: run_gc (orchestrate.c:275) | |
| ==4664== by 0x4F374B0: MVM_gc_enter_from_allocator (orchestrate.c:373) | |
| ==4664== by 0x4F3761F: MVM_gc_allocate_nursery (allocation.c:31) | |
| ==4664== by 0x4F3765D: MVM_gc_allocate_zeroed (allocation.c:48) | |
| ==4664== by 0x4F377E5: MVM_gc_allocate_object (allocation.c:84) | |
| ==4664== by 0x4F48973: allocate (P6opaque.c:111) | |
| ==4664== by 0x4F404C3: MVM_repr_clone (reprconv.c:28) | |
| ==4664== by 0x4F221F5: MVM_frame_invoke (frame.c:289) | |
| ==4664== by 0x4F49EBF: invoke_handler (MVMCode.c:10) | |
| ==4664== Address 0x158 is not stack'd, malloc'd or (recently) free'd | |
| ==4664== | |
| ==4664== | |
| ==4664== Process terminating with default action of signal 11 (SIGSEGV): dumping core | |
| ==4664== Access not within mapped region at address 0x158 | |
| ==4664== at 0x4F3CC0C: push_work_to_thread_in_tray (collect.c:390) | |
| ==4664== by 0x4F3D25F: process_worklist (collect.c:458) | |
| ==4664== by 0x4F3D59A: MVM_gc_collect (collect.c:87) | |
| ==4664== by 0x4F36E26: run_gc (orchestrate.c:275) | |
| ==4664== by 0x4F374B0: MVM_gc_enter_from_allocator (orchestrate.c:373) | |
| ==4664== by 0x4F3761F: MVM_gc_allocate_nursery (allocation.c:31) | |
| ==4664== by 0x4F3765D: MVM_gc_allocate_zeroed (allocation.c:48) | |
| ==4664== by 0x4F377E5: MVM_gc_allocate_object (allocation.c:84) | |
| ==4664== by 0x4F48973: allocate (P6opaque.c:111) | |
| ==4664== by 0x4F404C3: MVM_repr_clone (reprconv.c:28) | |
| ==4664== by 0x4F221F5: MVM_frame_invoke (frame.c:289) | |
| ==4664== by 0x4F49EBF: invoke_handler (MVMCode.c:10) | |
| ==4664== If you believe this happened as a result of a stack | |
| ==4664== overflow in your program's main thread (unlikely but | |
| ==4664== possible), you can try to increase the size of the | |
| ==4664== main thread stack using the --main-stacksize= flag. | |
| ==4664== The main thread stack size used in this run was 8388608. | |
| ==4664== | |
| ==4664== HEAP SUMMARY: | |
| ==4664== in use at exit: 140,872,610 bytes in 504,322 blocks | |
| ==4664== total heap usage: 926,210 allocs, 421,888 frees, 370,332,950 bytes allocated | |
| ==4664== | |
| ==4664== LEAK SUMMARY: | |
| ==4664== definitely lost: 767,946 bytes in 12,559 blocks | |
| ==4664== indirectly lost: 279,945 bytes in 1,416 blocks | |
| ==4664== possibly lost: 24,384 bytes in 56 blocks | |
| ==4664== still reachable: 139,800,335 bytes in 490,291 blocks | |
| ==4664== suppressed: 0 bytes in 0 blocks | |
| ==4664== Rerun with --leak-check=full to see details of leaked memory |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment