On Fri, 22 Jun 2001, Christian Robottom Reis wrote:
>
> Hi,
>
> I'm getting pygtk2 to build against CVS gtk, and it works find - or sort
> of. When I run hello2.py, for example, it renders fine, but SEGVs on exit.
> Stack trace follows. I remember James saying something about this, but I
> just can't remember :-) James, if I can help you with this, let me know,
> ok?
>
> (gdb) r hello2.py
> Starting program: /usr/local/bin/python hello2.py
> Gtk-Message: YOU ARE USING THE DEVEL BRANCH 1.3.x OF GTK+ WHICH IS
> CURRENTLY
> UNDER HEAVY DEVELOPMENT AND FREQUENTLY INTRODUCES
> INSTABILITIES.
> if you don't know why you are getting this, you probably
> want to
> use the stable branch which can be retrived from
> ftp://ftp.gtk.org/pub/gtk/v1.2/ or via CVS with
> cvs checkout -r glib-1-2 glib; cvs checkout -r gtk-1-2
> gtk+
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x80b5250 in PyFrame_New (tstate=0x0, code=0x81dbad8, globals=0x81a0e2c,
> locals=0x0) at Objects/frameobject.c:114
> 114 PyFrameObject *back = tstate->frame;
> (gdb) where
> #0 0x80b5250 in PyFrame_New (tstate=0x0, code=0x81dbad8,
> globals=0x81a0e2c,
> locals=0x0) at Objects/frameobject.c:114
> #1 0x806c941 in eval_code2 (co=0x81dbad8, globals=0x81a0e2c, locals=0x0,
> args=0x81e2d80, argcount=1, kws=0x0, kwcount=0, defs=0x0, defcount=0,
> closure=0x0) at Python/ceval.c:436
> #2 0x8070c5c in call_eval_code2 (func=0x81e3b94, arg=0x81e2d74, kw=0x0)
> at Python/ceval.c:2959
> #3 0x80708df in call_object (func=0x81e3b94, arg=0x81e2d74, kw=0x0)
> at Python/ceval.c:2799
> #4 0x80707e2 in PyEval_CallObjectWithKeywords (func=0x81e3b94,
> arg=0x81e2d74,
> kw=0x0) at Python/ceval.c:2734
> #5 0x80ade07 in PyObject_CallObject (o=0x81e3b94, a=0x81e2d74)
> at Objects/abstract.c:1529
> #6 0x400183f0 in pyg_closure_marshal (closure=0x829c9a0,
> return_value=0x0,
> n_param_values=1, param_values=0xbfffe554, invocation_hint=0xbfffe43c,
> marshal_data=0x0) at gobjectmodule.c:769
> #7 0x403d7977 in g_closure_invoke (closure=0x829c9a0, return_value=0x0,
> n_param_values=1, param_values=0xbfffe554, invocation_hint=0xbfffe43c)
> at gclosure.c:436
> #8 0x403e7a16 in signal_emit_unlocked_R (node=0x829bf08, detail=0,
> instance=0x829d858, emission_return=0x0,
> instance_and_params=0xbfffe554)
> at gsignal.c:2092
> #9 0x403e663d in g_signal_emit_valist (instance=0x829d858, signal_id=71,
> detail=0, var_args=0xbfffe7c4) at gsignal.c:1855
I haven't been able to reproduce this problem (it exits normally for me).
I haven't updated my copy of gtk today, but I doubt anything of interest
has changed there.
The bug appears to be caused by dereferencing a NULL python thread state
variable. I don't know why that would occur.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
