Emulator Issues #3913
closedDolphin 'hangs' when trying to start a game
0%
Description
What's the problem?
No game can be started. Hitting the Start button the wait cursor appears and the emulator hangs. Same when doing it via doubleclick.
Dolphin version with the problem: Version >= r6792
Operating system and version:
32bit redhat eles 5
32bit bol linux 5.1
32bit ubuntu natty 11.04
Game ID (as it appears in game properties, Ex.: "GZ2P01" or "RSBE01"):
I don't list a game because it seems to be a general problem with the gui. All my games have the problem...
Build command-line (not on Windows):
Yes, done a fresh svn checkout and build on commandline.
Was the ISO a plain dump from disc, compressed and/or scrubbed?
Plain
Please provide any additional information below.
Starting dolphin from within gdb there is no problem, I can start games as just before r6792.
In contrast attaching gdb while the application hangs, I have two threads, both showing following:
#0 0x00f36416 in __kernel_vsyscall ()
#1 0x0081752c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2 0x0823c6d4 in Common::Event::Wait(unsigned int) ()
#3 0x00000000 in ?? ()Starting it from within gdb there is no problem?
If I attach gdb while the application hangs, I have two threads, both showing following:
#0 0x00f36416 in __kernel_vsyscall ()
#1 0x0081752c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2 0x0823c6d4 in Common::Event::Wait(unsigned int) ()
#3 0x00000000 in ?? ()
If I copy back the MemoryUtil.cpp from r6791 it works again. Makes me totally mad because the file seems to be only reformatted and some pointers were renamed.
Updated by soren.jorvang almost 14 years ago
- Status changed from New to Accepted
Does it still happen with r6831?
Updated by Metzelmaennchen almost 14 years ago
Yes, I have done a checkout of r6832 :(
Updated by soren.jorvang almost 14 years ago
- Status changed from Accepted to Fixed
This issue was closed by revision r6836.
Updated by Metzelmaennchen almost 14 years ago
Yes, I can confirm that, problem is fixed.
Funny that it was the panic handler going into nirvana.