'Segmentation Fault' in Catapult (Linux)

By Pedrete

Expert (115)

Pedrete's picture

26-07-2014, 22:43

Hello!

I have a problem with last version of Catapult. When I run Catapult, after the scan of the machines, I get the error 'Segmentation Fault' ('Violacion de acceso' in Spanish), and the program doesn't run. Why?
If I run Openmsx from Konsole, the emulator runs quite well.

I am running Linux Mint KDE 17, with a GeForce GT and Nvidia propietary driver vers. 331.

Thanks!

Login or register to post comments

By Manuel

Ascended (15355)

Manuel's picture

26-07-2014, 23:25

Which version are you running exactly?

Also it helps if you run openmsx-catapult with gdb and make a back trace:

gdb openmsx-catapult
run
[steps to make it crash]
bt
paste output here!

By Pedrete

Expert (115)

Pedrete's picture

27-07-2014, 00:26

I am running Catapult version 0.10.0-1

This is shown in the screen when I run it with gdb:

Quote:

GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
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 "x86_64-linux-gnu".
Type "show configuration" for configuration details.
Para las instrucciones de informe de errores, vea:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Leyendo símbolos desde openmsx-catapult...(no se encontraron símbolos de depuración)hecho.
(gdb) run
Starting program: /usr/bin/openmsx-catapult
[Depuración de hilo usando libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Nuevo Thread 0x7fffed71f700 (LWP 3055)]
[Nuevo Thread 0x7fffecba7700 (LWP 3057)]
[Thread 0x7fffecba7700 (LWP 3057) terminado]
[Nuevo Thread 0x7fffecba7700 (LWP 4199)]

Program received signal SIGSEGV, Segmentation fault.
[Cambiando a Thread 0x7fffecba7700 (LWP 4199)]
0x00007ffff701674e in wxEvtHandler::AddPendingEvent(wxEvent&ampWink ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
(gdb) bt
#0 0x00007ffff701674e in wxEvtHandler::AddPendingEvent(wxEvent&ampWink ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#1 0x00007ffff7910133 in wxJoystickThread::Entry() ()
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-2.8.so.0
#2 0x00007ffff7015863 in wxThreadInternal:TonguethreadStart(wxThread*) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#3 0x00007ffff64a6182 in start_thread ()
from /lib/x86_64-linux-gnu/libpthread.so.0
#4 0x00007ffff61d330d in clone () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)

By Manuel

Ascended (15355)

Manuel's picture

27-07-2014, 16:00

OK, that's not the latest version. Can you try with openMSX and Catapult 0.10.1?
Also, from the looks of it, the crash occurred not in Catapult but in the wxGTK library.