Seg fault in gr_filter_design

I was using the fresh-from-git gr_filter_design, and when I went to save
the results, I got a seg fault. Here’s some backtrace info from GDB:

from /usr/lib64/libQtGui.so.4

#24 0x00007f0d9316ef06 in ?? ()
from /usr/lib64/python2.7/site-packages/PyQt4/QtGui.so
#25 0x0000003a18d5d0dc in QCoreApplication::notifyInternal(QObject*,
QEvent*)
() from /usr/lib64/libQtCore.so.4
#26 0x0000003cc6fbac65 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEv—Type to continue, or q to quit—
ent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) ()
from /usr/lib64/libQtGui.so.4
#27 0x0000003cc7039984 in ?? () from /usr/lib64/libQtGui.so.4
#28 0x0000003cc7037e19 in QApplication::x11ProcessEvent(_XEvent*) ()
from /usr/lib64/libQtGui.so.4
#29 0x0000003cc705faf6 in ?? () from /usr/lib64/libQtGui.so.4
#30 0x00007f0d93858e33 in g_main_context_dispatch ()
from /lib64/libglib-2.0.so.0
#31 0x00007f0d93859610 in ?? () from /lib64/libglib-2.0.so.0
#32 0x00007f0d938598ad in g_main_context_iteration ()
from /lib64/libglib-2.0.so.0
#33 0x0000003a18d882cf in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)
() from /usr/lib64/libQtCore.so.4
#34 0x0000003cc705f7fe in ?? () from /usr/lib64/libQtGui.so.4
#35 0x0000003a18d5c472 in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib64/libQtCore.so.4
#36 0x0000003a18d5c6bc in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib64/libQtCore.so.4
#37 0x0000003a18d60b7b in QCoreApplication::exec() ()
from /usr/lib64/libQtCore.so.4
#38 0x00007f0d9316fc6b in ?? ()
from /usr/lib64/python2.7/site-packages/PyQt4/QtGui.so
#39 0x000000340cae965b in PyEval_EvalFrameEx ()
—Type to continue, or q to quit—
from /usr/lib64/libpython2.7.so.1.0
#40 0x000000340caea71d in PyEval_EvalFrameEx ()
from /usr/lib64/libpython2.7.so.1.0
#41 0x000000340caeb04d in PyEval_EvalCodeEx ()
from /usr/lib64/libpython2.7.so.1.0
#42 0x000000340caeb162 in PyEval_EvalCode ()
from /usr/lib64/libpython2.7.so.1.0
#43 0x000000340cb0639c in ?? () from /usr/lib64/libpython2.7.so.1.0
#44 0x000000340cb071d0 in PyRun_FileExFlags ()
from /usr/lib64/libpython2.7.so.1.0
#45 0x000000340cb07daf in PyRun_SimpleFileExFlags ()
from /usr/lib64/libpython2.7.so.1.0
#46 0x000000340cb198ce in Py_Main () from /usr/lib64/libpython2.7.so.1.0
#47 0x00000033f2e1ee5d in __libc_start_main () from /lib64/libc.so.6
#48 0x0000000000400649 in _start ()

I’m running Fedora 14 on a x86_64 platform


Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

On Wed, Oct 31, 2012 at 1:39 PM, Marcus D. Leech [email protected]
wrote:

QMouseEv—Type to continue, or q to quit—
from /lib64/libglib-2.0.so.0
#37 0x0000003a18d60b7b in QCoreApplication::exec() ()
#42 0x000000340caeb162 in PyEval_EvalCode ()

I’m running Fedora 14 on a x86_64 platform


Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

My guess is a problem with an older version of QT. Can you tell me
what version you’re running on?

Tom

#26 0x0000003cc6fbac65 in QApplicationPrivate::sendMouseEvent(QWidget*,
#32 0x00007f0d938598ad in g_main_context_iteration ()
/usr/lib64/libQtCore.so.4
from /usr/lib64/libpython2.7.so.1.0

what version you’re running on?

Tom

qt-webkit-4.7.4-7.fc14.x86_64
qt-assistant-adp-4.6.3-1.fc14.x86_64
gambas2-gb-qt-ext-2.23.0-1.fc14.x86_64
qt-4.7.4-7.fc14.x86_64
qwtplot3d-qt4-devel-0.2.7-9.fc12.x86_64
gambas2-gb-qt-opengl-2.23.0-1.fc14.x86_64
qtoctave-0.10.1-7.fc14.x86_64
dbusmenu-qt-0.6.3-1.fc14.1.x86_64
qt-x11-4.7.4-7.fc14.x86_64
qt-qsa-1.1.5-7.fc12.x86_64
gambas2-gb-qt-kde-2.23.0-1.fc14.x86_64
qwtplot3d-qt4-0.2.7-9.fc12.x86_64
qtiplot-0.9.8.3-1.fc14.x86_64
qt-devel-4.7.4-7.fc14.x86_64
R-qtl-1.21.2-1.fc14.x86_64
polkit-qt-0.99.0-2.fc14.x86_64
qt3-3.3.8b-37.fc14.x86_64
gambas2-gb-qt-kde-html-2.23.0-1.fc14.x86_64
gambas2-gb-qt-2.23.0-1.fc14.x86_64


Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs