![]() |
PyGTK / glade strange issue
Hello,
I'm using glade-3 to build my GUI. And I have a strange behaviour. I often get a seg. fault when opening the File menu on my main window. When I have such crash, all I have to do is to save again the glade file, and then rebuild the package, without any other modification. But this bug comes back very often, when I make modifications in my GUI. A few days ago, I had a bigger problem: my app didn't start anymore on OS2008 (but work fine os OS2007). I discovered that it crashes when calling the wTree.signal_autoconnect() method. In fact, the problem comes from these lines in the signal dict: Code:
{... So, I think that the problem comes from the glade file, and might be related to the other one. Does anyone has experienced such problem? How can I debug it? Thanks for any idea. |
Re: PyGTK / glade strange issue
Did you get any warnings or error in the console ? (it s mean running your soft without python launcher or run it with python2.5)
|
Re: PyGTK / glade strange issue
Yes, sorry, I forgot to post them. Here are are the warning when I have the signals defined in the auto-connection dict:
Code:
/usr/lib/python2.5/site-packages/papywizard/controller/abstractController.py:120: Warning: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed |
Re: PyGTK / glade strange issue
Hum ...
From what i understand, this is an error raise by libglade ... it s look like there is a null object ... : 1) The object you try to link with your methods doesn't exist anymore. (.destroy ?) 2) The object you try to link doesn't have this signal 3) The object you try to link isn't a gobject ... does it come from hildon ? 4) Something is broken in your python binding install (old version ? as there is a old bug on a old version (see:http://lists.maemo.org/pipermail/mae...er/030798.html)) |
Re: PyGTK / glade strange issue
Ok, I think I understand... This is because of reparenting the GUI with a hildon window; it is done *before* I connect the signals, so my initial dialog, defined in glade, does not exists anymore :rolleyes:
What I don't understand, is how it could work on OS2007 (gtk2.10), and not in OS2008 (2.12)... I would expect the opposite. Anyway, thank you very much :) For the File menu crash, there is not warning... It just silently seg. fault. The crash occurs on all maemo plateforms (this time, but on a previous version, users reported that it was working for them, while others had the crash)... Any idea? How can I debug this problem? |
Re: PyGTK / glade strange issue
for the why ... i think the libglade version on the last diablo version doesn't support very well hildon :)
and for the file menu ... i don't see, ... many times a seg fault in python is due to some thread problem ... else it's raise an error :) But it s can also be a binding problem. |
Re: PyGTK / glade strange issue
Any idea how I could dig to find what causes the problem in the C code? what tool could I use for that? Are there some lib versions which output logs?
|
Re: PyGTK / glade strange issue
I added a callback on that File menu, on the activate signal, to see when the crash occurs. It seems that it occurs *after* the signal is emited.
|
Re: PyGTK / glade strange issue
Another warning I addn't before (and I don't have on other plateforms): when opening the config dialog, I get:
Code:
/usr/lib/python2.5/site-packages/papywizard/controller/abstractController.py:92: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed |
Re: PyGTK / glade strange issue
No idea ... could you send me the source ? maybe i could look in it ...
|
All times are GMT. The time now is 06:01. |
vBulletin® Version 3.8.8