matplotlib segfault

[Adam Mercer]

On Thu, Mar 6, 2008 at 12:28 PM,  <skip at pobox.com> wrote:
> I finally got py25-matplotlib installed.  Like an earlier poster though I
>  get a segfault with the TkAgg backend.  Running under gdb gives me the
>  barest of information though since nothing appears to be built with debug
>  symbols enabled:
>
>     #0  0x01f0bf40 in TclpFree ()
>     #1  0x01f0807e in ResetObjResult ()
>     #2  0x01fc08c6 in Tk_MainWindow ()
>     #3  0x01e832e0 in PyAggImagePhoto ()
>     #4  0x01eb5aeb in TclInvokeStringCommand ()
>     #5  0x0a010518 in TclEvalObjvInternal ()
>     #6  0x0a0108fb in Tcl_EvalObjv ()
>     #7  0x01aed848 in Tkapp_Call ()
>     #8  0x00234e5f in PyEval_EvalFrameEx ()
>     #9  0x00236baa in PyEval_EvalCodeEx ()
>     #10 0x002349c3 in PyEval_EvalFrameEx ()
>     #11 0x00236baa in PyEval_EvalCodeEx ()
>     #12 0x002349c3 in PyEval_EvalFrameEx ()
>     #13 0x00236baa in PyEval_EvalCodeEx ()
>     #14 0x001c41ea in function_call ()
>     #15 0x0019f922 in PyObject_Call ()
>     #16 0x00233021 in PyEval_EvalFrameEx ()
>     #17 0x00236baa in PyEval_EvalCodeEx ()
>     #18 0x001c41ea in function_call ()
>     #19 0x0019f922 in PyObject_Call ()
>     #20 0x001a8676 in instancemethod_call ()
>     #21 0x0019f922 in PyObject_Call ()
>     #22 0x0022e196 in PyEval_CallObjectWithKeywords ()
>     #23 0x01aebd4c in PythonCmd ()
>     #24 0x0a00d7cf in TclInvokeStringCommand ()
>     #25 0x0a010518 in TclEvalObjvInternal ()
>     #26 0x0a05839c in TclExecuteByteCode ()
>     #27 0x0a061088 in Tcl_ExprObj ()
>     #28 0x0a010de5 in Tcl_ExprBooleanObj ()
>     #29 0x0a01beb5 in Tcl_IfObjCmd ()
>     #30 0x0a010518 in TclEvalObjvInternal ()
>     #31 0x0a011645 in TclEvalEx ()
>     #32 0x0a011f3e in Tcl_EvalEx ()
>     #33 0x0b007f01 in Tk_BindEvent ()
>     #34 0x0b00de59 in TkBindEventProc ()
>     #35 0x0b0162fa in Tk_HandleEvent ()
>     #36 0x0b033c3a in TkDoConfigureNotify ()
>     #37 0x0b033da9 in Tk_MakeWindowExist ()
>     #38 0x0b033ee8 in Tk_MapWindow ()
>     #39 0x0b02a4b2 in ArrangePacking ()
>     #40 0x0a0ac658 in TclServiceIdle ()
>     #41 0x0a08e2ea in Tcl_DoOneEvent ()
>     #42 0x01aeb4f6 in Tkapp_MainLoop ()
>     #43 0x00234e5f in PyEval_EvalFrameEx ()
>     #44 0x00236baa in PyEval_EvalCodeEx ()
>     #45 0x002349c3 in PyEval_EvalFrameEx ()
>     #46 0x00236baa in PyEval_EvalCodeEx ()
>     #47 0x002349c3 in PyEval_EvalFrameEx ()
>     #48 0x00236baa in PyEval_EvalCodeEx ()
>     #49 0x00236cb7 in PyEval_EvalCode ()
>     #50 0x0025a8e4 in PyRun_InteractiveOneFlags ()
>     #51 0x0025ab23 in PyRun_InteractiveLoopFlags ()
>     #52 0x0025b329 in PyRun_AnyFileExFlags ()
>     #53 0x00269848 in Py_Main ()
>     #54 0x00001f7c in _start ()
>     #55 0x00001ea9 in start ()
>
>  Is this enough for someone to debug with?  If not, how do I go about
>  installing debug versions of the various packages?  Is another interactive
>  backend supported for matplotlib?

There are the wxpython and gtk2 variants. Give those a try, this is a
strange problem as I am unable to reproduce these segfaults on Intel
Leopard.

Cheers

Adam