Re: [Boa Constr] cvs boa core dumps on RedHat 6.1/wx 2.1.3

[Riaan B. <riaan@e.co.za>]

Hi Jeff,	

Jeff Turner wrote:
> 
> Has anyone seen the following behavior?  have a workaround?
> 
> first, my configuration:
> 
>   RedHat 6.1 (x86)
>   gtk 1.2.6
>   wxGTK 2.1.13
>   wxPython 2.1.13
>   python 1.5.2
> 

My config looks almost exactly the same,

   RedHat 6.1
   gtk+ 1.2.5-2
   wxGTK 2.1.13-0
   wxPython 2.1.13-1
   python 1.5.2-7

All installed from rpms.

> the problem:
> 
> When i try to run the latest CVS version of Boa (or boa 0.0.3)
> i get a segmentation fault during startup.  the problem occurs
> the first time anyone tries to create a wxImageList (in the case
> of running "python Boa.py", that occurs during parsing of
> Debugger.BreakViewCtrl)
> 

Bill Eldridge has reported a similar problem. He has narrowed it down
to wxBitmaps. I've suggested what I could think of but nothing has helped. 
It's a bit tricky as I don't have the problem (obviously).

I have a theory at the moment that for you guys the wxApp has to be 
instanciated before wxBitmaps for some strange reason.

> i assume the problem is some sort of wx startup race condition.
> if i add the following code, before any of the imports, in Boa.py,
> i don't get the core dump.
> 
> #
> # XXX sjt - this seems to keep us from core dumping
> #
> from wxPython.wx import *
> class DummyApp(wxApp):
>     def OnInit(self):
>         return true
> dummy = DummyApp()

I've reordered the code of Boa.py so that the app is created before anything
else is imported (what you intended), find it attached and please give me
feedback.

> 
> Although that avoids the core dump, it runs into a second problem, an
> infinite supply of the following message, and no windows ever
> pop up (i've only ever waited about 4-5 minutes before killing it)
> 
> GLib-CRITICAL **: file gmain.c: line 500 (g_source_remove): assertion
> `tag > 0' failed.
> 
> GLib-CRITICAL **: file gmain.c: line 500 (g_source_remove): assertion
> `tag > 0' failed.
> 
> ...
> ...
> 
> I don't know if the two problems are related or not.
> 
> any clues?
> 
> thanks,
> jeff
> 

I have no idea what the CRITICALs mean, it probably has something to do 
with the fact that you have two app objects. I get the same if I 
instanciate wxApp twice under wxGTK. (which when done while a wxApp is 
in a MainLoop would give the error: Only 1 wxApp per process)
Creating two apps before entering one's MainLoop works without a hitch on
wxMSW. (Not that you would want to do that)

Hope the attached file helps.

Riaan