segmentation fault under mandrake 9.1

[Kurbster]

Whenever I run pcsx from the terminal, it always comes up with a segmentation fault after clicking OK on the startup dialog box. This image should sum up everything....

[linuzappz]

hi, tried compiling Pcsx from the sources? if not try :)

[ammoQ]

I'm almost sure it's not a problem in pcsx, but in libgpuPeteMesaGL.so.1.0.61; this one crashes pcsx when pcsx calls it to get it's name and type. Removing it from the Plugin directory helped, but how to play then? libgpuPeteMesaGL.so.1.0.61 seems to crash epsxe also on MDK9.1

edit: The solution is described in the readme.txt of Pete's current plugin, just use
libpthread-0.10.so instead of libpthread-0.9.so

edit: the actions above make gpuPeteMesa work with Mandrake, but cause padJoy to crash in multithreaded mode, since padJoy would need the /lib/i686/ version of libpthread.so. To work around this, disable the multithreaded feature of padJoy; it will have little or no impact on most machines.

[expl]

hello,

i've the same problem .. when i download the pcsx build and start pcsx via ./pcsx, i must configure pcsx .. but when i press any button .. pcsx segfaults .. when i get the sources from the gentoo portage i've again segfaults but then the config frontend cant start ... dunno what the problem is ..


# find / -iname "*libpthread*"
/usr/lib/libpthread.so
/usr/lib/libpthread_nonshared.a
/usr/lib/libpthread.a
/lib/libpthread-0.10.so
/lib/libpthread.so.

[FLaRe85]

So that was the problem I was having in 9.1!

[expl]

mhh .. that means that smth else causes the segfault eh? :) .. but what is the solution for my problem?

or .. is there another psx emulator .. if yes .. less better than pcsx?

[PowerMacG4]

pcsx latest 1.6 also segfaults on Mac OS X. I believe there is a problem with gtkgui.c.

[expl]

hmm i think it could be a /gtk/ related problem . or/and GPU-plugin prob .. because gdb tells me that errors occured in loadGPUplugin() and loadplugins() ..

[MoJo]

This is a BUG of PCSX. I'm 100% sure! I'm using RedHat and sometimes I encounter that bug. Here is some hints to avoid:
- Get into PCSX folder before running pcsx
- In plugin menu choosing, never left any dialog box empty (the plugins are not in correct path)
- Chmod your PCSX to non-read only mode so all your changes applied will be saved.
I've known this bug for long time but frustratedly to say I don't think PCSX will have a chance to fix it anymore. Seems to me no one care about PCSX. ePSXe is killing its pal!