![]() |
| . Forums . Statistics . Sign Up . Search . |
| Yabause community forums / Bug reports / Segmentation fault with SDL Joypad Linux |
| Author | Message |
| Enji Member |
# Posted: 2 Apr 2009 20:43 Fedora 10 Cambridge on x86 Dell Latitude 120L SIGSEGV's whenever I try to configure the SDL input for my gamepad here's my gdb output: gdb yabause GNU gdb Fedora (6.8-29.fc10) Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... (gdb) run Starting program: /usr/local/bin/yabause [Thread debugging using libthread_db enabled] [New Thread 0xb7fdc700 (LWP 25622)] Can't set translation file [New Thread 0xb6b29b90 (LWP 25692)] Program received signal SIGSEGV, Segmentation fault. 0x003da849 in SDL_JoystickUpdate () from /usr/lib/libSDL-1.2.so.0 Missing separate debuginfos, use: debuginfo-install OpenEXR-libs-1.6.1-4.fc10.i386 SDL-1.2.13-7.fc10.i386 alsa-lib-1.0.19-2.fc10.i386 bzip2-libs-1.0.5-3.fc10.i386 dbus-libs-1.2.4-2.fc10.i386 e2fsprogs-libs-1.41.4-4.fc10.i386 expat-2.0.1-5.i386 fontconfig-2.6.0-3.fc10.i386 freetype-2.3.7-2.fc10.i386 gamin-0.1.9-6.fc10.i386 glib2-2.18.4-1.fc10.i386 glibc-2.9-3.i686 ilmbase-1.0.1-2.fc9.i386 jasper-libs-1.900.1-9.fc10.i386 kdelibs-4.2.1-4.fc10.i386 keyutils-libs-1.2-3.fc9.i386 krb5-libs-1.6.3-16.fc10.i386 lcms-libs-1.18-1.fc10.i386 libICE-1.0.4-4.fc10.i386 libSM-1.1.0-2.fc10.i386 libX11-1.1.5-2.fc10.i386 libXau-1.0.4-1.fc10.i386 libXcursor-1.1.9-3.fc10.i386 libXdamage-1.1.1-4.fc9.i386 libXdmcp-1.0.2-6.fc10.i386 libXext-1.0.4-1.fc9.i386 libXfixes-4.0.3-4.fc10.i386 libXft-2.1.13-1.fc10.i386 libXi-1.1.3-4.fc9.i386 libXinerama-1.0.3-2.fc10.i386 libXpm-3.5.7-4.fc9.i386 libXrandr-1.2.3-1.fc10.i386 libXrender-0.9.4-3.fc9.i386 libXtst-1.0.3-3.fc9.i386 libXxf86vm-1.0.2-1.fc10.i386 libacl-2.2.47-3.fc10.i386 libattr-2.4.43-2.fc10.i386 libcap-2.10-2.fc10.i386 libdrm-2.4.0-0.21.fc10.i386 libgcc-4.3.2-7.i386 libjpeg-6b-43.fc10.i386 libmng-1.0.9-7.i386 libpng-1.2.35-1.fc10.i386 libselinux-2.0.78-1.fc10.i386 libstdc++-4.3.2-7.i386 libtiff-3.8.2-11.fc10.i386 libxcb-1.1.91-5.fc10.i386 libxml2-2.7.3-1.fc10.i386 mesa-dri-drivers-7.2-0.15.fc10.i386 mesa-libGL-7.2-0.15.fc10.i386 mesa-libGLU-7.2-0.15.fc10.i386 openssl-0.9.8g-12.fc10.i686 qt-4.4.3-15.fc10.i386 qt-x11-4.4.3-15.fc10.i386 strigi-libs-0.6.4-3.fc10.i386 zlib-1.2.3-18.fc9.i386 (gdb) bt #0 0x003da849 in SDL_JoystickUpdate () from /usr/lib/libSDL-1.2.so.0 #1 0x0809474e in PERSDLJoyScan (n=0x8915d80 "Up") at persdljoy.c:227 #2 0x0807c94d in UIPadSetting::timer_timeout (this=0xbfffd138) at ui/UIPadSetting.cpp:180 #3 0x080840e5 in UIPadSetting::qt_metacall (this=0xbfffd138, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfffca68) at build/release/.moc/moc_UIPadSetting.cpp:70 #4 0x0384bdf0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #5 0x0384cb72 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #6 0x03886c37 in QTimer::timeout () from /usr/lib/libQtCore.so.4 #7 0x0385279e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4 #8 0x038468cf in QObject::event () from /usr/lib/libQtCore.so.4 #9 0x0664568c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #10 0x0664d4ce in QApplication::notify () from /usr/lib/libQtGui.so.4 #11 0x038371c1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #12 0x03865081 in ?? () from /usr/lib/libQtCore.so.4 #13 0x038618a0 in ?? () from /usr/lib/libQtCore.so.4 #14 0x00a71238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #15 0x00a748e3 in ?? () from /lib/libglib-2.0.so.0 ---Type <return> to continue, or q <return> to quit--- #16 0x00a74aa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #17 0x038617f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #18 0x066de515 in ?? () from /usr/lib/libQtGui.so.4 #19 0x0383588a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #20 0x03835a4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #21 0x06ab1297 in QDialog::exec () from /usr/lib/libQtGui.so.4 #22 0x08076d78 in UIPortManager::tbSetJoystick_clicked (this=0x89c4930) at ui/UIPortManager.cpp:141 #23 0x08083ff0 in UIPortManager::qt_metacall (this=0x89c4930, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfffd33c) at build/release/.moc/moc_UIPortManager.cpp:73 #24 0x0384bdf0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #25 0x0384c1f0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #26 0x06c32761 in QAbstractButton::clicked () from /usr/lib/libQtGui.so.4 #27 0x06985ab9 in ?? () from /usr/lib/libQtGui.so.4 #28 0x06987694 in ?? () from /usr/lib/libQtGui.so.4 #29 0x06987926 in QAbstractButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4 #30 0x06a6441c in QToolButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4 #31 0x0669d6f2 in QWidget::event () from /usr/lib/libQtGui.so.4 ---Type <return> to continue, or q <return> to quit--- #32 0x0698595e in QAbstractButton::event () from /usr/lib/libQtGui.so.4 #33 0x06a63ee4 in QToolButton::event () from /usr/lib/libQtGui.so.4 #34 0x0664568c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #35 0x0664de81 in QApplication::notify () from /usr/lib/libQtGui.so.4 #36 0x038371c1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #37 0x0664d10e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #38 0x066b7456 in ?? () from /usr/lib/libQtGui.so.4 #39 0x066b67e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #40 0x066dee1a in ?? () from /usr/lib/libQtGui.so.4 #41 0x00a71238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #42 0x00a748e3 in ?? () from /lib/libglib-2.0.so.0 #43 0x00a74aa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #44 0x038617f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #45 0x066de515 in ?? () from /usr/lib/libQtGui.so.4 #46 0x0383588a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #47 0x03835a4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #48 0x06ab1297 in QDialog::exec () from /usr/lib/libQtGui.so.4 ---Type <return> to continue, or q <return> to quit--- #49 0x08054371 in UIYabause::on_aFileSettings_triggered (this=0x829ba38) at ui/UIYabause.cpp:230 #50 0x08082e15 in UIYabause::qt_metacall (this=0x829ba38, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfffe3bc) at build/release/.moc/moc_UIYabause.cpp:138 #51 0x0384bdf0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #52 0x0384c1f0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #53 0x0663f391 in QAction::triggered () from /usr/lib/libQtGui.so.4 #54 0x0663fcff in QAction::activate () from /usr/lib/libQtGui.so.4 #55 0x06a63f22 in QToolButton::nextCheckState () from /usr/lib/libQtGui.so.4 #56 0x06987653 in ?? () from /usr/lib/libQtGui.so.4 #57 0x06987926 in QAbstractButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4 #58 0x06a6441c in QToolButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4 #59 0x0669d6f2 in QWidget::event () from /usr/lib/libQtGui.so.4 #60 0x0698595e in QAbstractButton::event () from /usr/lib/libQtGui.so.4 #61 0x06a63ee4 in QToolButton::event () from /usr/lib/libQtGui.so.4 #62 0x0664568c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #63 0x0664de81 in QApplication::notify () from /usr/lib/libQtGui.so.4 #64 0x038371c1 in QCoreApplication::notifyInternal () ---Type <return> to continue, or q <return> to quit--- from /usr/lib/libQtCore.so.4 #65 0x0664d10e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 |
| Hatta Member |
# Posted: 11 Apr 2009 17:59 Is anything else using the gamepad? I was just having a similar problem, turns out I had left mupen64plus running on another desktop. Killing it and restarting yabause allowed me to configure my gamepad. |
| darklegion Member |
# Posted: 29 Sep 2009 05:32 . Edited by: darklegion I get the same issue with current svn on linux (using the qt port).I tried the GTK port, but it launches with a completely grey window, with no options visible and this message: "(yabause:11877): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed" |
|
Powered by miniBB forum software © 2001-2010 |