|
|
|||||||
| About Us | Register | FAQ | Members List | Calendar | Mark Forums Read |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
#1 (permalink) |
|
I want you INSIDE me
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Join Date: Mar 2002
Location: Massachusetts, USA
Posts: 8,365
|
segmentation fault under mandrake 9.1
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....
__________________
![]() Kirby's AnimeDB list AMD Athlon64 X2 4400+ Toledo, Nvidia GeForce 7950GT SLi, 2GB PC3200 2-3-2-5, ABit AN8-SLi, Sound Blaster X-FI XtremeMusic |
|
|
|
|
|
#3 (permalink) |
|
Emu author
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Join Date: Mar 2002
Location: Vienna/Austria/Europe
Posts: 1,168
|
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.
__________________
If you think my English is bad, wait till you read my Polish. Last edited by ammoQ; May 18th, 2003 at 18:35. |
|
|
|
|
|
#4 (permalink) |
|
Registered User
Join Date: Dec 2003
Posts: 3
|
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 .. Code:
# find / -iname "*libpthread*" /usr/lib/libpthread.so /usr/lib/libpthread_nonshared.a /usr/lib/libpthread.a /lib/libpthread-0.10.so /lib/libpthread.so. |
|
|
|
|
|
#5 (permalink) |
|
I Need a Weapon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Join Date: Oct 2001
Location: Omaha, NE
Posts: 4,300
|
So that was the problem I was having in 9.1!
__________________
.: Flaretech.Net :: Flaretech.Biz Web Hosting :: H3 Stats :: My Blog :.
![]() .: Macbook Pro 17" :: 2.33 GHz Intel Core 2 Duo :: 2 GB 667 MHz DDR2 :: ATI Radeon X1600 :. .: AMD Athlon X2 4400+ @ 2.42 GHz :: OCZ 2 GB Platinum DDR400 :: eVGA NVIDIA GeForce 7800 GT :. .: Home Server :: 2.41 GHz AMD Opteron 180 :: 4 GB DDR400 :: Windows Server 2008 Standard RC0 :. |
|
|
|
|
|
#9 (permalink) |
|
Golden Condom
![]() ![]() ![]() Join Date: Nov 2002
Location: 日本
Posts: 379
|
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!
__________________
>> IBM Thinkpad X61 << OS: Ubuntu Ibex Intrepid SVN |
|
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|