I *think* this is due to wxPython not being compiled properly. This
error is usually due to not setting up threads context properly before
calling Python code. This probably means that wxPython was compiled
without threads support, but python was compiled with threads support.
(It can also mean that there was a missing threads setup call in the
wxPython code, but that code seems to be correct and your line numbers
match mine).
Configuring wxPython is rather complex. I *thought* this was configured
automatically, but maybe not. There is a define named "WXP_WITH_THREAD"
that is defined in wxPython/include/wx/wxPython/wxPython_int.h that
controls this.
Anyway, you might try running the wxPython demos to see what happens.
Make sure to do something that takes events. If those do not work, it's
likely a miscompile.
FYI, this traceback shows window destructors being called from the idle
loop. I assume the domain open dialog window is being destroyed. The
code is attempting to setup a python frame to do something in python,
and it crashed setting up this frame. Every time I've seen this before
it has been due to my missing a thread setup call in OpenIPMI before
calling python code. However, since there is no OpenIPMI code in the
traceback, that's not the case here.
A few other things to try:
* I'm running with python 2.4.1. Maybe it's a problem in your
python version?
* Can you open a domain with the target not available (unplug the
network cord from the target)? If not, it is almost certainly a
wxPython configuration problem. If so, can you save the
preferences, plug the network cord back into the target, then
restart the GUI? It should automatically connect to the target
without a dialog.
I've been questioning my choice of using wxPython for the GUI. I like
it in general, but there have been lots of little issues like this...
-Corey
[EMAIL PROTECTED] wrote:
>
>
> ------------------------------------------------------------------------
> *From:* atca ipmi
> *Sent:* Mon 3/20/2006 11:58 AM
> *To:* Corey Minyard
> *Subject:* RE: [Openipmi-developer] OpenIPMI GUI
>
> Hello,
>
> We have tried the patch, but the segmentation fault persists. Please
> find below the full backtrace.
>
> (gdb) bt
> #0 0x080c2f28 in PyFrame_New ()
> #1 0x0807ad8e in PyEval_EvalCodeEx ()
> #2 0x080c447c in PyFunction_SetClosure ()
> #3 0x080b3797 in PyObject_Call ()
> #4 0x080ba4ab in PyMethod_New ()
> #5 0x080b3797 in PyObject_Call ()
> #6 0x0807c2d0 in PyEval_CallObjectWithKeywords ()
> #7 0x08060cfc in PyType_GenericNew ()
> #8 0x08060dbf in PyType_GenericNew ()
> #9 0x080ce68b in PyDict_Clear ()
> #10 0x401ec512 in wxPyOORClientData_dtor (self=0x8c2ed18) at
> src/helpers.cpp:961
> #11 0x401f22c0 in ~wxPyOORClientData (this=0x8c2ed18) at
> wxPython_int.h:494
> #12 0x408b11a5 in wxEvtHandler::~wxEvtHandler() () from
> /usr/local/lib/libwx_base-2.6.so.0
> #13 0x406a8f88 in wxWindowBase::~wxWindowBase() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #14 0x405b4277 in wxWindow::~wxWindow() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #15 0x406ce643 in wxPanel::~wxPanel() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #16 0x41130b69 in ~wxPyScrolledWindow (this=0x8c2ed28) at htmlwin.h:71
> #17 0x406a9687 in wxWindowBase::DestroyChildren() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #18 0x405b424d in wxWindow::~wxWindow() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #19 0x406ce6a4 in wxPanel::~wxPanel() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #20 0x406a9687 in wxWindowBase::DestroyChildren() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #21 0x405b424d in wxWindow::~wxWindow() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #22 0x406ce6a4 in wxPanel::~wxPanel() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #23 0x406a9687 in wxWindowBase::DestroyChildren() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #24 0x405b424d in wxWindow::~wxWindow() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #25 0x406a2fdb in wxTopLevelWindowBase::~wxTopLevelWindowBase() ()
> from /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #26 0x405ad323 in wxTopLevelWindowGTK::~wxTopLevelWindowGTK() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #27 0x405ff4a0 in wxDialog::~wxDialog() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #28 0x406252c0 in wxAppBase::DeletePendingObjects() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #29 0x40625498 in wxAppBase::OnIdle(wxIdleEvent&) () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #30 0x4081c77a in wxAppConsole::HandleEvent(wxEvtHandler*, void
> (wxEvtHandler::*)(wxEvent&), wxEvent&) const ()
> from /usr/local/lib/libwx_base-2.6.so.0
> #31 0x408b17f9 in
> wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&,
> wxEvtHandler*, wxEvent&) ()
> from /usr/local/lib/libwx_base-2.6.so.0
> ---Type <return> to continue, or q <return> to quit---
> #32 0x408b0cd9 in wxEventHashTable::HandleEvent(wxEvent&,
> wxEvtHandler*) () from /usr/local/lib/libwx_base-2.6.so.0
> #33 0x408b1968 in wxEvtHandler::ProcessEvent(wxEvent&) () from
> /usr/local/lib/libwx_base-2.6.so.0
> #34 0x40625381 in wxAppBase::ProcessIdle() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #35 0x4058c68a in wxapp_idle_callback () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #36 0x40d82743 in g_timeout_add () from /usr/lib/libglib-2.0.so.0
> #37 0x40d7fb35 in g_get_current_time () from /usr/lib/libglib-2.0.so.0
> #38 0x40d80b78 in g_main_context_dispatch () from
> /usr/lib/libglib-2.0.so.0
> #39 0x40d80e8d in g_main_context_dispatch () from
> /usr/lib/libglib-2.0.so.0
> #40 0x40d8158f in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
> #41 0x40aa7f5f in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
> #42 0x405a3082 in wxEventLoop::Run() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #43 0x40625047 in wxAppBase::MainLoop() () from
> /usr/local/lib/libwx_gtk2_core-2.6.so.0
> #44 0x401e8623 in wxPyApp::MainLoop() (this=0x8ac76d8) at
> src/helpers.cpp:150
> #45 0x40230071 in _wrap_PyApp_MainLoop (args=0x8a5450c,
> kwargs=0x8b6be3c) at src/gtk/_core_wrap.cpp:23098
> #46 0x080d0e8e in PyCFunction_Call ()
> #47 0x080b3797 in PyObject_Call ()
> #48 0x0807cb13 in PyEval_GetFuncDesc ()
> #49 0x0807aaa1 in PyEval_EvalCode ()
> #50 0x0807b0ce in PyEval_EvalCodeEx ()
> #51 0x080c447c in PyFunction_SetClosure ()
> #52 0x080b3797 in PyObject_Call ()
> #53 0x080ba4ab in PyMethod_New ()
> #54 0x080b3797 in PyObject_Call ()
> #55 0x0807c905 in PyEval_GetFuncDesc ()
> #56 0x0807a525 in PyEval_EvalCode ()
> #57 0x0807b0ce in PyEval_EvalCodeEx ()
> #58 0x0807c62b in PyEval_GetFuncDesc ()
> #59 0x0807a5a3 in PyEval_EvalCode ()
> #60 0x0807b0ce in PyEval_EvalCodeEx ()
> #61 0x0807c62b in PyEval_GetFuncDesc ()
> #62 0x0807a5a3 in PyEval_EvalCode ()
> #63 0x0807b0ce in PyEval_EvalCodeEx ()
> #64 0x08077fc5 in PyEval_EvalCode ()
> #65 0x08097e29 in PyRun_FileExFlags ()
> ---Type <return> to continue, or q <return> to quit---
> #66 0x08096d90 in PyRun_SimpleFileExFlags ()
> #67 0x080966da in PyRun_AnyFileExFlags ()
> #68 0x08053a19 in Py_Main ()
> #69 0x08053469 in main ()
> #70 0x400bb44d in __libc_start_main () from /lib/libc.so.6
>
> Regards,
> Tina
> ------------------------------------------------------------------------
> *From:* Corey Minyard [mailto:[EMAIL PROTECTED]
> *Sent:* Mon 3/20/2006 2:03 AM
> *To:* atca ipmi
> *Cc:* [email protected]
> *Subject:* Re: [Openipmi-developer] OpenIPMI GUI
>
> I was able to do some more testing and shake loose a few more problems
> and fix them. It doesn't look like it will solve the problem you are
> having, but it's work a shot. The ChangeLog should describe the updates
> made. Patch is attached...
>
> And a full traceback will be most handy, if this doesn't solve the
> problem.
>
> -Corey
>
> [EMAIL PROTECTED] wrote:
>
> > Hello,
> >
> > This is with regard to a problem we face while running the GUI
> > provided along with OpenIPMI - 2.0.6. On running " make rungui " from
> > the OpenIPMI base directory, the GUI comes up. But on adding the shelf
> > manager as a domain, using the add domains options, it connects and
> > starts retrieving information but immediately closes displaying a
> > segmentation fault.
> >
> > We are using wxPython-2.6.1.0.There is no such problem while
> > connecting and retrieving information using impish.
> >
> > On taking core dump and running backtrace on it, it shows the
> > occurrence of segmentation fault after the following last lines:
> >
> > #66 0x08096d90 in PyRun_SimpleFileExFlags ()
> >
> > #67 0x080966da in PyRun_AnyFileExFlags ()
> >
> > #68 0x08053a19 in Py_Main ()
> >
> > #69 0x08053469 in main ()
> >
> > #70 0x400bb44d in __libc_start_main () from /lib/libc.so.6.
> >
> > Kindly provide your suggestions on this issue.
> >
> > Regards,
> >
> > Tina
> >
> >
> >
>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Openipmi-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openipmi-developer
