[pypy-issue] [issue787] Crash in the assembler backend when running Django

[Alex Gaynor]

New submission from Alex Gaynor <alex.gaynor at gmail.com>:

As seen under gdb:


alex at alex-gaynor-laptop:~/projects/django$ PYTHONPATH=`pwd` gdb --args 
~/projects/pypy/pypy-c tests/runtests.py --settings=test_sqlite 
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/alex/projects/pypy/pypy-c...(no debugging symbols 
found)...done.
(gdb) run
Starting program: /home/alex/projects/pypy/pypy-c tests/runtests.py --
settings=test_sqlite
[Thread debugging using libthread_db enabled]
Creating test database for alias 'default'...
Creating test database for alias 'other'...
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
.................s..............................................................
.......s...
Program received signal SIGSEGV, Segmentation fault.
0x000000000097dc2c in pypy_g_encode_rex___72.clone.0 ()
(gdb) bt
#0  0x000000000097dc2c in pypy_g_encode_rex___72.clone.0 ()
#1  0x000000000097dfdf in pypy_g_encode__star_2_14 ()
#2  0x0000000000e88254 in pypy_g_Assembler386_assemble_bridge ()
#3  0x0000000000dc3ca0 in pypy_g_send_bridge_to_backend ()
#4  0x0000000000d30d88 in pypy_g_compile_new_bridge ()
#5  0x0000000000c07922 in pypy_g_MetaInterp_compile_done_with_this_frame ()
#6  0x0000000000b64feb in pypy_g_MetaInterp_finishframe ()
#7  0x0000000000a5cfd3 in pypy_g_handler_ref_return ()
#8  0x000000000098aca2 in pypy_g_MIFrame_run_one_step ()
#9  0x00000000009335a8 in pypy_g_MetaInterp__interpret ()
#10 0x00000000008d3969 in pypy_g_MetaInterp_interpret ()
#11 0x0000000000f5b443 in pypy_g_MetaInterp__handle_guard_failure ()
#12 0x0000000000f63cab in pypy_g_MetaInterp_handle_guard_failure ()
#13 0x00000000008bb17b in pypy_g_assembler_call_helper_1 ()
#14 0x00007ffff3a1b901 in ?? ()
#15 0x0000000000000003 in ?? ()
#16 0xffffffffffffffff in ?? ()
#17 0x0000000003096f00 in ?? ()
#18 0x00007ffff4fd8da0 in ?? ()
#19 0x0000000000000000 in ?? ()





This is semi-reproducible, when running Django I usually see either it, or an 
RPython error in force_virtual.

----------
messages: 2754
nosy: agaynor, pypy-issue
priority: bug
status: unread
title: Crash in the assembler backend when running Django

________________________________________
PyPy bug tracker <tracker at bugs.pypy.org>
<https://bugs.pypy.org/issue787>
________________________________________