[PR #3516] [CLOSED] Log SIGBUS signals #3534

New issue

Closed

opened 2026-02-27 22:04:03 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 22:04:03 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/shadps4-emu/shadPS4/pull/3516
Author: @kalaposfos13
Created: 9/4/2025
Status: ❌ Closed

Base: main ← Head: dont-ignore-sigbus

📝 Commits (1)

1864691 Log SIGBUS signals

📊 Changes

1 file changed (+4 additions, -2 deletions)

View changed files

📝 src/core/signals.cpp (+4 -2)

📄 Description

Currently, if SIGBUS is hit, it'll just get silently skipped, which is not desirable if for example a game enters into an infinite loop of raising SIGBUS on a single instruction. I wasn't sure if I should make this an unreachable though, but given that so far no one complained about randomly hitting this while using a debugger, it might be the better choice, especially given that all three cases I've this this being hit the games either crashed anyway immediately after or hung. It should be mentioned that out of the three cases, two was messing around with things that changed memory allocations such as isNeo, and the third time was on PS4 Linux

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/shadps4-emu/shadPS4/pull/3516 **Author:** [@kalaposfos13](https://github.com/kalaposfos13) **Created:** 9/4/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `dont-ignore-sigbus` --- ### 📝 Commits (1) - [`1864691`](https://github.com/shadps4-emu/shadPS4/commit/18646912b295d2ec5a1d0ed3d5340f471ef62284) Log SIGBUS signals ### 📊 Changes **1 file changed** (+4 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `src/core/signals.cpp` (+4 -2) </details> ### 📄 Description Currently, if SIGBUS is hit, it'll just get silently skipped, which is not desirable if for example a game enters into an infinite loop of raising SIGBUS on a single instruction. I wasn't sure if I should make this an unreachable though, but given that so far no one complained about randomly hitting this while using a debugger, it might be the better choice, especially given that all three cases I've this this being hit the games either crashed anyway immediately after or hung. It should be mentioned that out of the three cases, two was messing around with things that changed memory allocations such as isNeo, and the third time was on PS4 Linux --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>