dolphin on fedora 13

[Marcel Wijlaars]

I'm new with dolphin-emu and trying to get dolphin -emu to work on my fedora 13 machine.
I have a few questions:
Should the current SVN trunk work on a linux box, more specifically the fedora 13 distribution?
Doplin-emu compiles just fine however segfaults when I try running a game (original DVD or iso file both segfault ). Is there a kind of manual or HOWTO about how to debug dolphin-emu?

Thanks in advance

Marcel Wijlaars

[neobrain]

Dolphin (recent revisions included)should run fine on Linux (recent distro releases included).
Not sure what goes wrong, but it'd be great if you debugged the problem and opened up an issue at our google code page.

Debugging works like this:
run scons like "scons flavor=Debug ." (or flavor=debug, not sure).
Then, inside the terminal, run "ulimit -c unlimited". IIRC this sets the stack limit to unlimited (which is needed for debugging).
Then, inside the same terminal session, run the dolphin binary (note that it might be located in a separete linux-x86_64-debug folder). When it crashes, a crash report will be created (usually called "core"). With that one, you can get additional information about the crash using gdb. Just run gdb dolphin-emu core. type "bt" and post the output here or in the google code issue. There's not much you can do otherwise without some understanding in terms of programming and/or debugging.

[Marcel Wijlaars]

(09-16-2010, 07:41 AM)NeoBrain Wrote: Dolphin (recent revisions included)should run fine on Linux (recent distro releases included).
Not sure what goes wrong, but it'd be great if you debugged the problem and opened up an issue at our google code page.

Debugging works like this:
run scons like "scons flavor=Debug ." (or flavor=debug, not sure).
Then, inside the terminal, run "ulimit -c unlimited". IIRC this sets the stack limit to unlimited (which is needed for debugging).
Then, inside the same terminal session, run the dolphin binary (note that it might be located in a separete linux-x86_64-debug folder). When it crashes, a crash report will be created (usually called "core"). With that one, you can get additional information about the crash using gdb. Just run gdb dolphin-emu core. type "bt" and post the output here or in the google code issue. There's not much you can do otherwise without some understanding in terms of programming and/or debugging.

The backtrace looks like this:
#0 0x00000000420af733 in ?? ()
#1 0x0000000040adb087 in ?? ()
#2 0x0000000000000003 in ?? ()
#3 0x0000000000000003 in ?? ()
#4 0x0000000000000000 in ?? ()

gdb says: Missing separate debuginfo for plugins/*.so, how do I make the symols visable?

[neobrain]

hm, I'm not sure whether it actually compiled with debugging symbols... make sure it really uses the debug flavor and that during compilation (you might need to enable some verbose switch for this) the -g flag is passed to gcc. Apart from that you're close to giving me some usuable information