lr-pcsx-rearmed: runcommand.sh: line 804: 5728 Segmentation fault (since 3.8)
-
Unfortunately that may be the best option. I forgot to mention I'm running retropie on a pi3, in case it's relevant. Also, the log I posted was truncated and didn't actually show the error message. Here's a full log:
Starting PCSX-ReARMed v3.0rc1-1125-g4e6f4e9
Running PCSX Version 1.9 (May 26 2016).
psxMap: warning: wanted to map @80000000, got 0x73950000
Init new dynarec
testing if we can run recompiled code..
test passed.
warning: RAM is not directly mapped, performance will suffer
Mapped (RAM/scrp/ROM/LUTs/TC):
77000000/1f800000/1fc00000/08000000/744fe000
found BIOS file: SCPH1001.BIN
RGB565 supported, using it
plugin: plugins/builtin_gpu
plugin: plugins/builtin_spu
plugin: plugins/builtin_pad
plugin: plugins/builtin_pad
Plugins loaded.
Loaded CD Image: /home/osmc/RetroPie/roms/psx/Xenogears (USA) (Disc 1).cue[+cue].
Track 01 (DATA) - Start 00:02:00, Length 67:54:36
/opt/retropie/supplementary/runcommand/runcommand.sh: line 804: 5728 Segmentation fault /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-pcsx-rearmed/libretro.so --config /opt/retropie/configs/psx/retroarch.cfg "/home/osmc/RetroPie/roms/psx/Xenogears (USA) (Disc 1).cue" --appendconfig /tmp/retroarch.cfg -
https://retropie.org.uk/forum/topic/3/read-this-first - please use markdown or an external site for posting log snippets
I will wait and see if @dankcushions comes up with a fix first.
-
I was about to post the same issue.
For the record I've been working on enabling ffmpeg recording in retroarch, and happened to create a complete scratch build yesterday, not knowing 3.8 was just released.The system is a pi3, Raspbian image from 10th May, fully updated/upgraded as the base, with the latest RetroPie manually installed from binaries.
After setting the controller type to 'analog' in lr-pcsx-rearmed via rgui, all subsequent launches of any psx title cause a segmentation fault, reported in /tmp/run command.log
The issue can be reverted by editing
/opt/RetroPie/configs/all/retroarch-core-options.cfg- changing:
pcsx_rearmed_pad1type="analog" - back to:
pcsx_rearmed_pad1type="standard"
[Edit]
Whilst the above edit of the .cfg allows the emulator to load games once more, the retroarch menu is broken - 'main menu' is devoid of entries.
If I resolve this I'll update this post again.[Edit 2]
A reinstall of lr-pcsx-rearmed from source, via the retropie_setup.sh script restored the retroarch menu.The latest source doesn't fix the main issue (not unexpectedly), in that selecting 'analog' as pad1 type triggers segmentation faults on loading the emulator.
Strangely, after editing the .cfg file again, the emulator not only loaded games again, but the retroarch menu was intact.
- changing:
-
I also ran into this issue. Reverting the controller back to standard as described by @RetroResolution worked around the issue for me.
-
hi all,
i'm the guy who commit the multitap support, i see this bug when i developped the multitap support, if you set a controller with the analog option and try to launch pcsx rearmed without a controler wwith 2 analog sticks configured, the library crash. if all is configured (2 sticks L3 R3) they have no problem to launch a game. the type of controler set to standard fix the problem, i will look like this on the code, how to reproduce the crash and try to fix it. -
@alexis-puska hi, thanks for the update
I forgot to mention in my post that my controller is a PlayStation 1 Dualshock - as such it has no L3 R3 to configure. Not sure if that's significant, but thought I'd note it anyway.
-
Normaly ps1 dualshock has the L3 and R3 buttons, when you press the 2 analog joystick you have a button. can you configure your controller whith all button (analog stick and L3, R3) and test it ?
-
@alexis-puska I understand. In Emulation Station I configured the dualshock, in analog mode, and definitely pressed the analog sticks in - all inputs appear to be mapped.
Should I specifically configure the duaslshock from within the rgui menu?
Currently I'm switching between two different RetroPie builds, one is on 3.7, the other on 3.8, so I can test things in both versions if that helps.
-
just configure the pad in analog in retroarch by config file or by the rgui. if all button is mapped, the analog pad type don't crash pcsx rearmed. i think, i can saying a mistake, i don't know but retroarch don't provide the state of analog pad type if L3 R3 and the two axis of a analog pad is not configured. i'm in work office, i can't test, can you ?
-
I can confirm changing the controller to standard on core-options the emulator can run.
But I'm afraid I have all buttons mapped, including both analog sticks and the L3 and R3 buttons.
I have a cheap controller that is recognized and a keyboard, including the different directions of the analog sticks. -
i have made some test this night, with a clean install of retropie. i have 2 xin mo controller without analog sticks with arcade buttons, and other controler with analog stick. if i activate the analog mode on the xin mo controller (pad 0 and pad 1) -> crash.
if i activated the analog without all buttons configured on controller with analog pad -> launch.
i think the code crash when i get the key state of the analog value when the pad is not configured or compatible with analog mode, retroarch crush when i request the state.
if you want to play for the moment use standard pad in your config file. i look that this week-end. -
@alexis-puska sounds like a plan - thanks for your efforts on this
-
I have rebuilt the RetroPie lr-pcsx-rearmed binaries to a version before the most recent changes until this is sorted.
-
@BuZz excellent, thanks!
-
Hey guys, I'm also having a segmentation fault error.. but I'm new to this all, and not sure exactly whats going on
here is a copy of my log file. can anyone help me sort this?Starting PCSX-ReARMed v3.0rc1-1125-g4e6f4e9
Running PCSX Version 1.9 (May 26 2016).
Init new dynarec
testing if we can run recompiled code..
test passed.
Mapped (RAM/scrp/ROM/LUTs/TC):
80000000/1f800000/1fc00000/08000000/b4396000
found BIOS file: SCPH1001.BIN
RGB565 supported, using it
plugin: plugins/builtin_gpu
plugin: plugins/builtin_spu
plugin: plugins/builtin_pad
plugin: plugins/builtin_pad
Plugins loaded.
Loaded CD Image: /home/pi/RetroPie/roms/psx/SLUS_00551.CUE.
/opt/retropie/supplementary/runcommand/runcommand.sh: line 804: 819 Segmentation fault /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-pcsx-rearmed/libretro.so --config /opt/retropie/configs/psx/retroarch.cfg "/home/pi/RetroPie/roms/psx/SLUS_00551.CUE" --appendconfig /tmp/retroarch.cfg -
@skrapps914 there are two solutions in this thread which will work. easiest is just going to the retropie-setup menu, and reinstalling lr-pcsx-rearmed from binaries.
-
@dankcushions i saw the first solution, which was
"The issue can be reverted by editing
/opt/RetroPie/configs/all/retroarch-core-options.cfgchanging:
pcsx_rearmed_pad1type="analog"
back to:
pcsx_rearmed_pad1type="standard""however, my retroarch-core-options.cfg does't have any lines for pcsx_rearmed at all. (i'm guessing thats where the issue is, seems like pcsx rearmed isnt writing to the config file?
the second solution, reinstalling from binaries, i have no idea how to do.. i'm new to all of this.
-
@skrapps914 i suspect your issue isn't anything to do with this, then. you should instead give us more details: https://retropie.org.uk/forum/topic/3/read-this-first
-
Hi,
Regarding installation of the PlayStation emulator from binaries, maybe this guide will help:
RetroPie Manual Installation Guide, including the Version 4 Setup Script Revised Menu Structure
When following the guide, In the section Installing the Main Emulators, rather than using the option "Install/Update all main packages from binary", instead select the lr-pcsx-rearmed emulator from the list
-
@dankcushions i followed instructions the correct way, i put the bios in the bios folder, i created a disc image from one of my playstation games, transfered the bin/cue files to the psx roms folder. i went to start it, and got this error in the log
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.