[pypy-issue] [issue1609] SIGSEGV at startup if compiled with ICC

Greg Czajkowski tracker at bugs.pypy.org
Wed Sep 18 01:10:12 CEST 2013

New submission from Greg Czajkowski <gregczajkowski at yahoo.com>:

How can I rebuild pypy with debug symbols? I'm getting a crash right at startup
if it's compiled with ICC

Program received signal SIGSEGV, Segmentation fault.
0x00000000013471cc in pypy_g_walk_to_parent_frame ()
(gdb) bt
#0  0x00000000013471cc in pypy_g_walk_to_parent_frame ()
#1  0x0000000001346f51 in pypy_g__asm_callback ()
#2  0x00000000015a5b3d in pypy_asm_stackwalk ()
#3  0x0000000001340889 in pypy_g_MiniMarkGC_minor_collection ()
#4  0x000000000133df51 in pypy_g_MiniMarkGC_setup ()
#5  0x0000000001347ed1 in pypy_g_frameworkgc_setup ()
#6  0x0000000000412c16 in RPython_StartupCode ()
#7  0x000000000159eec8 in main ()

messages: 6180
nosy: gcflymoto, pypy-issue
priority: bug
release: 2.1
status: unread
title: SIGSEGV at startup if compiled with ICC

PyPy bug tracker <tracker at bugs.pypy.org>

More information about the pypy-issue mailing list