Previous Thread
Next Thread
Print Thread
Page 4 of 9 1 2 3 4 5 6 7 8 9
Joined: Dec 2009
Posts: 24
F
Member
Member
F Offline
Joined: Dec 2009
Posts: 24
Got my N900 this week and tried out the armel build of sdlmame. The program begins to load and the console screen pops up briefly but then it crashes.

Here's a the last bit of -verbose
Quote
etting SDL_VIDEO_GL_DRIVER = '' ...
Build version: 0.135u3 (Dec 26 2009)
Build architecure: SDLMAME_ARCH=
Build defines 1: SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1 SDLMAME_NOASM=1
Build defines 1: LSB_FIRST=1 NDEBUG=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1212 USE_OPENGL=0
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=2 __GNUC_PATCHLEVEL__=1 __VERSION__="4.2.1"
Compiler defines B: __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver : x11
SDL Monitor Dimensions: 800 x 480
Using SDL single-window soft driver (SDL 1.2)
Keyboard: Start initialization
Input: Adding Kbd #1: System keyboard
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding Mouse #1: System mouse
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Joystick: End initialization
Audio initialized - driver: pulse, frequency: 48000, channels: 2, samples: 512
sdl_create_buffers: creating stream buffer of 57344 bytes
ouput: unable to open output notifier file /tmp/sdlmame_out
Illegal instruction

Joined: Feb 2007
Posts: 507
C
Senior Member
Senior Member
C Offline
Joined: Feb 2007
Posts: 507
Which game did you try to run?

Given the "Illegal instruction", I recommend to compile with "OPTIMIZE=0 DEBUG=1" to get you started.

Joined: Mar 2001
Posts: 17,262
Likes: 267
R
Very Senior Member
Very Senior Member
R Offline
Joined: Mar 2001
Posts: 17,262
Likes: 267
What, no GDB backtrace? smile

Joined: Dec 2009
Posts: 24
F
Member
Member
F Offline
Joined: Dec 2009
Posts: 24
That was the startup of the front end with no ROM specified, and compiled with OPTIMIZE=0. I'm guessing the console front end is a custom ROM (hence the bad instruction) and that suggests a pretty fundamental corruption of emulation. Perhaps its due to the endless warning on type casts from the earlier post. And yes, i guess it's time to break out the debugger.

The same build parameters work fine in the scratchbox (x86) target.

Last edited by Flandry; 12/26/09 11:17 PM.
Joined: May 2009
Posts: 2,225
Likes: 387
J
Very Senior Member
Very Senior Member
J Offline
Joined: May 2009
Posts: 2,225
Likes: 387
Originally Posted by Flandry
I'm guessing the console front end is a custom ROM

Err... what?

Joined: Dec 2009
Posts: 24
F
Member
Member
F Offline
Joined: Dec 2009
Posts: 24
Originally Posted by Just Desserts
Originally Posted by Flandry
I'm guessing the console front end is a custom ROM

Err... what?

Ie what goes on when mame is run without specifying a ROM. For it to get an illegal instruction without even beginning an emulation there most be something exceptional about that code (pun intended).

Anyway, building with DEBUG=1 fails.

Code
Compiling src/osd/sdl/sdlos_unix.c...
src/osd/sdl/sdlos_unix.c: In function 'osd_break_into_debugger':
src/osd/sdl/sdlos_unix.c:117: warning: implicit declaration of function 'kill'
src/osd/sdl/sdlos_unix.c:117: error: 'SIGTRAP' undeclared (first use in this function)
src/osd/sdl/sdlos_unix.c:117: error: (Each undeclared identifier is reported only once
src/osd/sdl/sdlos_unix.c:117: error: for each function it appears in.)
make[1]: *** [obj/sdl/mamed/osd/sdl/sdlos_unix.o] Error 1

The debug will have to wait until i have time to see what's going on.

Last edited by Flandry; 12/26/09 11:22 PM.
Joined: Jan 2006
Posts: 3,694
Very Senior Member
Very Senior Member
Joined: Jan 2006
Posts: 3,694
Originally Posted by Flandry
Originally Posted by Just Desserts
Originally Posted by Flandry
I'm guessing the console front end is a custom ROM

Err... what?

Ie what goes on when mame is run without specifying a ROM. For it to get an illegal instruction without even beginning an emulation there most be something exceptional about that code (pun intended).

when you launch MAME without specifying game there is no custom ROM involved: it simply starts loading the empty driver from src/emu/drivers/empty.c (for your information, MAME could well support romless games with no problems, and indeed there are romless systems in MESS wink ).

Joined: Feb 2007
Posts: 507
C
Senior Member
Senior Member
C Offline
Joined: Feb 2007
Posts: 507
That's been mentioned before. Put a "include <signal.h>" in sdlos_unix.c. Without a stack trace honestly there is not much hope for support on a target which most (all?) devs do not have access to.

Joined: Jul 2006
Posts: 87
L
Member
Member
L Offline
Joined: Jul 2006
Posts: 87
Well I got a N900 for Chrismas, so I will probably give SDLMAME a try... once I have installed the SDK on my Fedora 11 64-bit that is.

Joined: Mar 2001
Posts: 17,262
Likes: 267
R
Very Senior Member
Very Senior Member
R Offline
Joined: Mar 2001
Posts: 17,262
Likes: 267
I've heard the N900 SDK is sufficiently Ubuntu-centric that on Fedora you're better off installing an Ubuntu VM image and running the SDK in that. Good luck smile

Page 4 of 9 1 2 3 4 5 6 7 8 9

Moderated by  R. Belmont 

Link Copied to Clipboard
Who's Online Now
3 members (Kale, MrBogi, AJR), 145 guests, and 4 robots.
Key: Admin, Global Mod, Mod
ShoutChat
Comment Guidelines: Do post respectful and insightful comments. Don't flame, hate, spam.
Forum Statistics
Forums9
Topics9,364
Posts122,482
Members5,082
Most Online1,283
Dec 21st, 2022
Our Sponsor
These forums are sponsored by Superior Solitaire, an ad-free card game collection for macOS and iOS. Download it today!

Superior Solitaire
Powered by UBB.threads™ PHP Forum Software 8.0.0