Project

General

Profile

Actions

Emulator Issues #6060

closed

Dolphin 3.5-5xx crashes in Ubuntu-x86

Added by shadowflash about 11 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

What did you expect to happen?
Normal game bootup
What steps will reproduce the problem?
Just try to run any game.
What version of Dolphin were you using?

What version of Dolphin used to work?
3.5-415, maybe a few revisions later.

Any other relevant information or links to logs:

(gdb) run
Starting program: /mnt/Files/Develop/dolphin-git/master/dolphin-emu/Binaries/dolphin-emu
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb42dcb40 (LWP 6402)]
[New Thread 0xb38ffb40 (LWP 6403)]
[New Thread 0xb134cb40 (LWP 6405)]

Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0xb134cb40 (LWP 6405)]
UpdateProjectionHack (iPhackvalue=0xc64d7b0, sPhackvalue=0xc64d7c0)
at /mnt/Files/Develop/dolphin-git/master/dolphin-emu/Source/Core/VideoCommon/Src/VertexShaderManager.cpp:118
118 float fhackvalue1 = 0, fhackvalue2 = 0;
(gdb) bt
#0 UpdateProjectionHack (iPhackvalue=0xc64d7b0, sPhackvalue=0xc64d7c0)
at /mnt/Files/Develop/dolphin-git/master/dolphin-emu/Source/Core/VideoCommon/Src/VertexShaderManager.cpp:118
#1 0x0871c817 in VideoConfig::UpdateProjectionHack (this=0xc64d760) at /mnt/Files/Develop/dolphin-git/master/dolphin-emu/Source/Plugins/Plugin_VideoOGL/Src/Render.cpp:84
#2 0x087186b0 in OGL::VideoBackend::Initialize (this=0xc842a78, window_handle=@0x8994df0: 0x46015f9)
at /mnt/Files/Develop/dolphin-git/master/dolphin-emu/Source/Plugins/Plugin_VideoOGL/Src/main.cpp:166
#3 0x081a84de in Core::EmuThread () at /mnt/Files/Develop/dolphin-git/master/dolphin-emu/Source/Core/Core/Src/Core.cpp:375
#4 0xb5ade007 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#5 0xb77b2d4c in start_thread (arg=0xb134cb40) at pthread_create.c:308
#6 0xb596ed3e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
(gdb)

Actions #1

Updated by parlane about 11 years ago

float fhackvalue1 = 0, fhackvalue2 = 0;

Confidence filling variable names eh..

Actions #2

Updated by parlane about 11 years ago

Going to need to know more details about the system you are using and what you used to compile this etc.

All I could find was http://stackoverflow.com/questions/12570374/floating-point-exception-sigfpe-on-int-main-return0

Actions #3

Updated by shadowflash about 11 years ago

Ok. It's Kubuntu 12.04.2 x86, gcc-4.6.3.
Machine - Phenom II X4 955 with Quadro 6000, hardware doesn't matter though - tried on my wife's laptop with intel cpu and AMD video card. Still crashes.
And 3.5-431 works just fine. I can try to go back from 3.5-549 with 3 revisions step until i'll get working build, and then go up by 1 until broken one will be found.

Actions #4

Updated by parlane about 11 years ago

Did you build it on your wife's computer? I'm thinking it's some weird compiler error. Or gdb is lying? Your gdb trace implies the floating point exception is on the initialization of a variable :\

Actions #5

Updated by shadowflash about 11 years ago

I'll try to build it in VirtualBox with Ubuntu 11.10 then. But... If it's compiler error then why everything before 5xx compiles just fine. Looking at changelog i can't find anything that can affect compiler in any way.

Actions #6

Updated by shadowflash about 11 years ago

Tried and it changed nothing. Different GCC version but still the same crash

Actions #7

Updated by parlane about 11 years ago

It's just that gdb is saying the error is:

float fhackvalue1 = 0, fhackvalue2 = 0;

Which is weird.

Actions #8

Updated by parlane about 11 years ago

We need some lower level data I think...

try this in gdb:

Print pc:
p/x $pc

Print 3 instructions at $pc:
x/3i $pc

After that we need a register dump too.

info registers

Also after that turn on asm totally with:
layout asm

And give us a dump of that screen. Thanks.

Btw we are on freenode at #dolphin-emu
IRC really helps with debugging these things live.

Actions #9

Updated by Sonicadvance1 about 11 years ago

Try f3528277c4ef

There was a rounding mode that wasn't being set correctly for FPU, could be the cause of this.

Actions #10

Updated by Sonicadvance1 about 11 years ago

  • Status changed from New to Fixed

This is fixed with f3528277c4ef, djibb confirmed my suspicions

Actions

Also available in: Atom PDF