Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[abrt] Mayavi-4.3.0-7.fc19: wxEvtHandler::SearchDynamicEventTable: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV) #87

Closed
opoplawski opened this issue Oct 16, 2013 · 8 comments

Comments

@opoplawski
Copy link

opoplawski commented Oct 16, 2013

https://bugzilla.redhat.com/show_bug.cgi?id=1018234

Description of problem:
The Mayavi2 (3D scientific data visualization and plotting tool) crashes.

To reproduce it:

  1. Open Mayavi2

  2. Add a Data Source

  3. Create a Point Load Source

  4. Add module or filter

  5. Click on Axes

After a few seconds, the program crashes. It happens every time.

Version-Release number of selected component:

Mayavi-4.3.0-7.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/bin/mayavi2
crash_function: wxEvtHandler::SearchDynamicEventTable
executable:     /usr/bin/python2.7
kernel:         3.11.3-201.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 wxEvtHandler::SearchDynamicEventTable at src/common/event.cpp:1412
 #1 wxEvtHandler::ProcessEvent at src/common/event.cpp:1297
 #3 wxScrollHelperEvtHandler::ProcessEvent at src/generic/scrlwing.cpp:208
 #4 wxEvtHandler::ProcessEvent at src/common/event.cpp:1308
 #6 gtk_window_button_press_callback at src/gtk/window.cpp:1634
 #7 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
 #12 gtk_widget_event_internal at gtkwidget.c:5017
 #13 gtk_widget_event at gtkwidget.c:4814
 #14 gtk_propagate_event at gtkmain.c:2490
 #15 gtk_main_do_event at gtkmain.c:1685

Any idea what might be causing this?

@GaelVaroquaux
Copy link
Contributor

Truncated backtrace:
Thread no. 1 (10 frames)
#0 wxEvtHandler::SearchDynamicEventTable at src/common/event.cpp:1412
#1 wxEvtHandler::ProcessEvent at src/common/event.cpp:1297
#3 wxScrollHelperEvtHandler::ProcessEvent at src/generic/scrlwing.cpp:208
#4 wxEvtHandler::ProcessEvent at src/common/event.cpp:1308
#6 gtk_window_button_press_callback at src/gtk/window.cpp:1634
#7 gtkmarshal_BOOLEAN__BOXED at gtkmarshalers.c:86
#12 gtk_widget_event_internal at gtkwidget.c:5017
#13 gtk_widget_event at gtkwidget.c:4814
#14 gtk_propagate_event at gtkmain.c:2490
#15 gtk_main_do_event at gtkmain.c:1685

Any idea what might be causing this?

From the stack trace, the bug is happening in Wx. To pin point it better,
could you retrieve the Python part of the stack trace (see
http://scipy-lectures.github.io/advanced/debugging/index.html#debugging-segmentation-faults-using-gdb
)

Thanks!

@pankajp
Copy link

pankajp commented Oct 16, 2013

The rhbz bug linked is not public.
Here's a full gdb backtrace: https://gist.github.com/pankajp/711e01334762421ada59

@opoplawski
Copy link
Author

Hmm, didn't notice that the bug was private. But hopefully the provided trace is enough.

@opoplawski
Copy link
Author

Fedora bug is now public.

@opoplawski
Copy link
Author

So, the reason it was made private is that this is an exploitable bug:

Likely crash reason: Jump to an invalid address
Exploitable rating (0-9 scale): 6

Since I suspect the vast majority of Mayavi users are analyzing data they generate themselves I'm not too worried about the security implications, but perhaps it makes it higher priority to fix.

@opoplawski
Copy link
Author

Full backtrace is in the original bug report - https://bugzilla.redhat.com/attachment.cgi?id=811139

@nmz787
Copy link

nmz787 commented Aug 1, 2014

Was this ever reported to wxPython-users or wxPython-dev?

@stefanoborini
Copy link
Contributor

As far as I can see, it's a wx problem. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants