[pypy-issue] Issue #2098: Segfault in pypy_g_IncrementalMiniMarkGC_visit (pypy/pypy)

Patrick Varley issues-reply at bitbucket.org
Fri Jul 24 14:55:05 CEST 2015


New issue 2098: Segfault  in pypy_g_IncrementalMiniMarkGC_visit
https://bitbucket.org/pypy/pypy/issues/2098/segfault-in

Patrick Varley:

# Environment #

* OS: OS X 10.10.4 (14E46)
* Python: 2.7.9 (295ee98b69288471b0fcf2e0ede82ce5209eb90b, Jun 02 2015, 18:26:45)
* Pypy: PyPy 2.6.0 with GCC 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53) Pypy was installed from homebrew.

# Problem #
I have a script that run successfully with Pypy 2.5.1, when I upgrade to Pypy 2.6.0, it sometimes produces a segfaults.

Here is the backtrace from the core dump:

```
(lldb) target create "/usr/local/bin/pypy" --core "/cores/core.59563"
warning: (x86_64) /cores/core.59563 load command 295 LC_SEGMENT_64 has a fileoff + filesize (0x2af9a000) that extends beyond the end of the file (0x2af99000), the segment will be truncated to match
warning: (x86_64) /cores/core.59563 load command 296 LC_SEGMENT_64 has a fileoff (0x2af9a000) that extends beyond the end of the file (0x2af99000), ignoring this section
Core file '/cores/core.59563' (x86_64) was loaded.
Process 0 stopped
* thread #1: tid = 0x0000, 0x0000000100eb47be libpypy-c.dylib`pypy_g_IncrementalMiniMarkGC_visit + 59, stop reason = signal SIGSTOP
    frame #0: 0x0000000100eb47be libpypy-c.dylib`pypy_g_IncrementalMiniMarkGC_visit + 59
libpypy-c.dylib`pypy_g_IncrementalMiniMarkGC_visit:
->  0x100eb47be <+59>: testb  $0x1, 0x3(%rax,%rcx)
    0x100eb47c3 <+64>: je     0x100eb47fe               ; <+123>
    0x100eb47c5 <+66>: movq   %r14, %rdi
    0x100eb47c8 <+69>: movq   %rbx, %rsi
(lldb) bt all
* thread #1: tid = 0x0000, 0x0000000100eb47be libpypy-c.dylib`pypy_g_IncrementalMiniMarkGC_visit + 59, stop reason = signal SIGSTOP
  * frame #0: 0x0000000100eb47be libpypy-c.dylib`pypy_g_IncrementalMiniMarkGC_visit + 59
    frame #1: 0x0000000100eb2869 libpypy-c.dylib`pypy_g_IncrementalMiniMarkGC_visit_all_objects_step + 79
    frame #2: 0x0000000100eb19ab libpypy-c.dylib`pypy_g_IncrementalMiniMarkGC_major_collection_step + 456
    frame #3: 0x0000000100eb0354 libpypy-c.dylib`pypy_g_IncrementalMiniMarkGC_collect_and_reserve + 290
    frame #4: 0x0000000100eb3b9d libpypy-c.dylib`pypy_g_IncrementalMiniMarkGC_malloc_fixedsize + 228
    frame #5: 0x0000000105100c1d

```

Unfortunately I will not be able to provide the core dump or the script as it contains sensitive information.  I'm happy to run any lldb command that is required to debug this further.




More information about the pypy-issue mailing list