[Python-apps-team] Bug#575536: [Enthought-Dev] mayavi2 segfaults under VNC

[Varun Hiremath]

reassign 575536 libwxgtk2.8-0
thanks

Hi Gael,

On Sun, 04 Apr, 2010 at 03:17:12PM +0200, Gael Varoquaux wrote:
> On Sun, Apr 04, 2010 at 02:31:49PM +0200, Gael Varoquaux wrote:
> > Another option would be if you can give me access (say VNC :>) to a box
> > for which running gdb exhibits the right segfault.
> 
> Cancel that, I had a few ideas of what to inspect and made progress
> without gdb. The following code produces a segfault and is a pure wx
> code:
> 
> ################################################################################
> import wx
> import wx.glcanvas
> 
> # every wx app needs an app
> app = wx.PySimpleApp()
> 
> # create the top-level frame, sizer and glcanvas
> frame = wx.Frame(None, -1, "test", size=(400,400))
> widget = wx.glcanvas.GLCanvas(frame, -1)
> sizer = wx.BoxSizer(wx.VERTICAL)
> sizer.Add(widget, 1, wx.EXPAND)
> frame.SetSizer(sizer)
> #import pdb; pdb.set_trace()
> frame.Layout()
> ################################################################################
> 
> Unless we are doing something in this code (it's pretty much a summary of
> what happens when we create a VTK render window), I guess that this means
> that the bug is not ours (pfff, saved :>).
> 
> I'd love feedback from more experienced wx/gl hackers: what are we doing
> wrong? What can be done to avoid the problem? What is actually going on
> (if someone knows)?
> 
> Should the bug be reassigned to wx?

Thanks a lot, that was quick! I'm reassigning the bug to wx. Let's see
what they have to say about this.

Also, could you tell us what version of wx are you using?

Thanks,
Varun