On Mon, 2008-02-11 at 07:18 +0100, Bart Martens wrote: > Hi Sam, > > Please read my message of 24 January again. I meant to ask you to try > this test: > > 1. rename ~/.xchat2 to something else > 2. start xchat > 3. load notify.py > > Then you should see that xchat no longer crashes. Then comparing the > old and new ~/.xchat2 directories should reveal interesting information.
Unfortunately, it's not that simple. With a fresh .xchat2 directory, and the notify plugin loaded, xchat will still crash. I looked into the code at the top of the stack frame. Python crashes in Objects/frameobject.c because tstate is NULL, but in the previous stack frame, Python/ceval.c line 2531, it is asserted that this is not the case. Maybe this is because python is compiled with NDEBUG defined? I actually don't see why Python has anything to do with this problem at all. While rendering the display, xchat tries to create a GdkPixmap with zero width; this causes a critical warning to be thrown, which (via the bowels of glib) causes PyErr_Warn to be called, which eventually results in the crash. It would be nice if frames 7 through 9 weren't garbage <sigh>. > > Regards, > > Bart Martens > -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
signature.asc
Description: This is a digitally signed message part
