search

libretro / fceu-next

Port of FCEUmm / FCEUX to Libretro.
14 stars 9 forks source link

Crash on OS X #3

Closed clobber closed 12 years ago

clobber commented 12 years ago

Getting this crash outside of Xcode: http://pastebin.com/YrpZfKbN

Looks like it might be related to Input though. Any idea about this?

0x000000010aa1510a INPUTC::Update(int, void*, int) + 26 (input.h:17) 0x000000010aa13e3f FCEU_UpdateInput() + 63 (input.cpp:246) 0x000000010a9db75b _ZL12update_inputv + 315 (libsnes.cpp:473) 0x000000010a9db4c9 snes_run + 89 (libsnes.cpp:482)

Themaister commented 12 years ago

You'd want a complete backtrace from GDB there. It is probably a NULL pointer, but hard to tell without without knowing exactly what's going on.

clobber commented 12 years ago

Let me know if this helps, assuming I set it up correctly: http://pastebin.com/b9XLWneJ

clobber commented 12 years ago

This trace data might be a little better: http://pastebin.com/GFVSRHXd

Themaister commented 12 years ago

0 INPUTC::Update (this=0x0, w=0, data=0x0, arg=0) at input.h:17

No locals.

1 0x000000010aa13e3f in FCEU_UpdateInput () at /Users/clobber/Documents/clobber/OpenEmu/FCEUX/fceux/src-fceux/input.cpp:245

No locals.

Indeed it is a NULL pointer (this = 0x0). Something is not being initialized. Are you calling snes_init()?

inactive123 commented 12 years ago

BTW - this is not particularly related to the issue you're having, but any particular reason you would want to use FCEUX instead of FCEUmm?

The PS3 and libsnes ports now commonly use FCEUmm (it's also in the tree - src-fceumm).

http://cah4e3.shedevr.org.ru/fceultra.php

This is an FCEU fork that is still in C, doesn't have all the TAS 'hacks', and is focused more on mapper/game compatibility. It's also a lot faster when low sound quality is enabled.

For now I think I'll still have FCEUX and FCEUmm both in the FCEU Next tree - but perhaps at a certain point I might want to decide which of the two can go - and right now I'm leaning on FCEUX being purged in the future - the hacks and the general messiness of it stand in stark contrast to FCEUmm, which is still more or less 'sane code' - and more importantly, the focus is on game compatibility/mapper completeness rather than frivolous TAS hacks for which we have no need anyway.

Anyway, just thought I would bring this up in case you didn't know you could also use FCEUmm in FCEU Next.

clobber commented 12 years ago

Themaister: Definitely calling snes_init()

twinaphex: I think I tried out FCEUX because I had less build errors on OS X. I wasn't aware that FCEUmm had much better mapper support - thanks. How does FCEUX/mm compare to Nestopia?

inactive123 commented 12 years ago

I don't know how they compare to be honest - I might be tempted to do a NEStopia port if there's a desire to have it.