Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash when injured? #174

Open
BatMahn opened this issue May 7, 2024 · 1 comment
Open

Crash when injured? #174

BatMahn opened this issue May 7, 2024 · 1 comment

Comments

@BatMahn
Copy link

BatMahn commented May 7, 2024

Have tried latest release (as well as compiling from source). On both macOS and a SteamDeck (via Desktop mode). Grabbed a rando ISO from archive.org for the game data (yes, I've also got legit copies, this was easier).

Game fires up, music works, can pick my character, exit the vault. First rat that hits me, instant crash. Try another run where I kill the rats first, then rip over to vault 15.. first enemy that hits me, instant crash too.

Can paste whole crash.. but perhaps this is useful? (macOS)

Parent Process: launchd [1]
User ID: 501

Date/Time: 2024-05-06 21:16:16.0759 -0600
OS Version: macOS 14.4.1 (23E224)
Report Version: 12
Anonymous UUID: F1DF0596-92EB-FC05-14B5-D830B59925F4

Sleep/Wake UUID: 49443E34-1974-4C7B-865E-F2CA14839877

Time Awake Since Boot: 18000 seconds
Time Since Wake: 536 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [15847]

VM Region Info: 0 is not in any region. Bytes before following region: 4305715200
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 100a40000-100c54000 [ 2128K] r-x/r-x SM=COW /Applications/Fallout/Fallout.app/Contents/MacOS/fallout-ce

@dje4321
Copy link

dje4321 commented Jun 9, 2024

This appears to be due to a null pointer exception based on the crash report provided. Will need the entire crash to properly look into it

https://stackoverflow.com/questions/8370468/debugging-segmentation-faults-on-a-mac
Using something like gdb or lldb to get a full stacktrace would be invaluable in determining the issue at fault.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants