Repository navigation
PPSA26578: sceLibcBacktraceGetBufferSize not implemented, abort after boot | Windows, i7-13700K, RTX 5060 #8308
Description
Description
After the libc imports reported in #7624 were resolved, PPSA26578 now starts and then aborts. The guest calls sceLibcBacktraceGetBufferSize, which is not implemented, so libc throws and the process terminates.
Error
libc: unhandled exception 'St13runtime_error' thrown from 00007ff89a2b113f
terminate called after throwing an instance of 'std::runtime_error'
what(): sceLibcBacktraceGetBufferSize_nid_postfix not implemented
FATAL: abort() (SIGABRT)
The call comes from the guest (Il2cppUserAssemblies.prx.guest.prx appears in the stack candidates).
Environment
- AnyPS5 version / commit:
- OS: Windows 11
- CPU: Intel Core i7-13700K
- GPU: NVIDIA GeForce RTX 5060 (driver )
- RAM: 32GB DDR5
- Extraction firmware: 13.42 (libs\ extracted from my own console)
- Game: PPSA26578 (<base / patched, version>), Unity/IL2CPP
Notes
- The four imports from PPSA26578: unresolved ELF imports from libc.prx (0xC0000139) | Windows, i7-13700K, RTX 5060, 32GB DDR5 #7624 (KwzEip7m6TM, 9G6z-nF6njg, h+J60RRlfnk, B2ZbqV9geCM) no longer fail in this build.
- The log also shows many
[exception] guest context signal=0x1elines at the same RIP before the abort, and some failed opens (il2cpp.usym, UnityCache/Shared/__info, result=0x80020002). The run continues after them, so I believe the abort is the only fatal error, but I am not sure what the signal=0x1e lines are.
Activity
MarcZX10 commentedon Oct 20, 2026
An open PR already implements
sceLibcBacktraceSelfandsceLibcBacktraceGetBufferSizeon Windows: #8137. Its hosted checks pass, but the Windows runtime job is skipped. I left a focused test-coverage suggestion on the PR to verify that the first frame is exactly the caller, not just somewhere in the same module. This issue appears covered by #8137, so there is no need for a duplicate implementation.JJenkx commentedon Oct 22, 2026
#8137, which implements \sceLibcBacktraceSelf\ and \sceLibcBacktraceGetBufferSize\ on Windows, has been merged, and current \main\ (6ef5a1c) has both in \core/libs/prx/libc/src/Backtrace.cpp. A rebuild from current \main\ should get past this abort. I haven't run PPSA26578 myself.
MarcZX10 commentedon Oct 22, 2026
The latest update confirms that #8137 is merged and its two exports are present on current
main; this closes the reported missing-symbol cause, though the title has not yet been rerun. Could you retry PPSA26578 on a fresh build from currentmainand share whether it passes the former backtrace stop or reaches a new failure? That result will tell us whether this issue can be closed or needs a separate report. AI-assisted review.MarcZX10 commentedon Oct 23, 2026
Current upstream
main(b9a8704095) now contains implementations of bothsceLibcBacktraceGetBufferSizeandsceLibcBacktraceSelffor Windows incore/libs/prx/libc/src/Backtrace.cpp; unsupported hosts still throw. This appears to address the missing-export crash reported here at the code level. I have not run PPSA26578, so this is not confirmation that the title now boots. Could you retest on currentmainand update the report with the result?EagleBearerYS commentedon Oct 25, 2026
@MurphylawdenINC we ran MOUSE: P.I. For Hire (PPSA26578) on current
main(2742004), with our own dump, on Windows 11 with an RTX 3070 Laptop GPU. It gets past both stops: the four libc imports from #7624, and thesceLibcBacktraceGetBufferSizeabort here. It reaches the first level and plays there with no fatal error.The
[exception] guest context signal=0x1elines: 0x1e is signal 30,SIGUSR1in FreeBSD's numbering. Each line is that signal being delivered to a guest thread that was waiting. The host records the context at the same place for every delivery, which is why the RIP repeats. They aren't errors: the walking run logged about 2,400 of them in 22 minutes and kept going.If a build of current
maingets you to the same place, this issue and #7624 can be closed. A new stop is worth its own issue, with its log line.oneandonlydean commentedon Oct 25, 2026
Fixed by #8137 (c8301bb), which implements sceLibcBacktraceSelf and sceLibcBacktraceGetBufferSize on Windows; confirmed above on current main with this title reaching gameplay. Closing. A different stop would be a new issue.