[pypy-dev] spotting pypy segfault

Maciej Fijalkowski fijall at gmail.com
Tue Jun 10 07:50:22 CEST 2008


It's a bit worse. It's infinite rec on C level somewhat. How did that
happen? A bug in our cycle analysis? Short part from gdb trace is
like:

#393 0x08cabd32 in pypy_g_W_Super_getattribute (l_self_19118=0xb72f37d8,
    l_name_136=0x97c3144) at implement_7.c:35032
#394 0x08bcf5c5 in pypy_g_BuiltinActivation_UwS_W_Super_ObjSpace_str__run_ (
    l_self_670=0x983ae94, l_scope_w_55=0xb71de804) at implement_6.c:174279
#395 0x081e9510 in pypy_g_BuiltinCode_funcrun (l_self_174=0x980a040,
    l_func_8=0x97ef6c0, l_args_28=0xb71de7ec) at implement.c:233924
#396 0x0805ff37 in pypy_g_funccall_star2 (l_self_2634=0x97ef6c0,
    l_stararg0_6=0xb72f37d8, l_stararg1_1=0xb71de7c4) at implement.c:11482
#397 0x0807f7f1 in pypy_g_get_and_call_function_star1 (l_w_descr_13=0x97ef6c0,
    l_w_obj_846=0xb72f37d8, l_stararg0_10=0xb71de7c4) at implement.c:30312
#398 0x0807dafd in pypy_g__handle_getattribute (l_w_descr_2=0x97ef6c0,
    l_w_obj_845=0xb72f37d8, l_w_name_60=0xb71de7c4) at implement.c:29216
#399 0x08062baf in pypy_g_getattr (l_w_obj_841=0xb72f37d8,
    l_w_name_59=0xb71de7c4) at implement.c:13316
#400 0x08cabd32 in pypy_g_W_Super_getattribute (l_self_19118=0xb72f37d8,
    l_name_136=0x97c3144) at implement_7.c:35032

How did that happen?

Cheers,
fijal



More information about the Pypy-dev mailing list