benmbrennan / mupen64plus

Automatically exported from code.google.com/p/mupen64plus
0 stars 0 forks source link

all video plugin SIGSEV on intel GMA X4500HD #253

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Describe your system:
 - Linux distribution: debian sid amd64, Xorg 7.4, intel GMA X4500HD (G45
chipset), quad-core processor (Q8400) with 4Gb ram.
 - Machine type: 64-bit
 - Mupen64Plus version: 1.5
- Plugins used:
Video : all, audio : JttL's, Input : blight's 

Describe the problem:
SIGSEV at emulation startup :
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
    errno = 0 (Succès)
    address = 0x00000000
                address not mapped to object

Please provide any additional information below.

Worked fine without video. I tried to run as root, in case it was a
permission problem, to no avail. stracing didn't show anything obvious.
What's strange is that no video plugin works, even with the lowest settings.

Original issue reported on code.google.com by nodens2...@gmail.com on 13 Aug 2009 at 9:31

GoogleCodeExporter commented 9 years ago
Probably the same problem as 
http://code.google.com/p/mupen64plus/issues/detail?id=266

Original comment by tomd...@gmail.com on 14 Sep 2009 at 2:53

GoogleCodeExporter commented 9 years ago
I can now confirm that this issue is related to intel GMA X4500HD driver : I 
added a
radeon card and it works fine with the radeon.

Cheers,

Original comment by nodens2...@gmail.com on 20 Sep 2009 at 8:58

GoogleCodeExporter commented 9 years ago
Can you please use valgrind and gdb to get a useful backtrace.

There is also a bug inside mesa <= 7.5.1 which will cause mupen64plus nearly
immediately to crash. Please try a new snapshot of mesa. Debian bug can be 
found at
http://bugs.debian.org/545085

Original comment by sven@narfation.org on 21 Sep 2009 at 2:57

GoogleCodeExporter commented 9 years ago
system problem, not a mupen64plus bug.

Original comment by richard...@gmail.com on 12 Jan 2010 at 10:27