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

Cemu crashes without a stack trace or any debugging related files when using ui to enable interpreter #1223

Open
hYdos opened this issue May 27, 2024 · 9 comments
Labels
bug Something isn't working

Comments

@hYdos
Copy link

hYdos commented May 27, 2024

Current Behavior

Cemu crashes without printing a stack trace

Expected Behavior

A stack trace should be printed in log.txt

Steps to Reproduce

Grab the latest release of Cemu
Crash a game
Observe the log.txt

System Info (Optional)

OS: Windows 10
GPU: RTX 2070 Super

Emulation Settings (Optional)

No response

Logs (Optional)

log.txt

Homebrew I am working on which is crashing (it will be missing files so it won't crash the same way mine does, but it has the same missing stacktrace behavior)
ReflectionMetaDumperWiiU.zip

@hYdos hYdos added the bug Something isn't working label May 27, 2024
@Exzap
Copy link
Member

Exzap commented May 27, 2024

Proper PPC stack traces can only be generated if Cemu is running in interpreter mode (by setting game profile CPU mode to interpreter or launch Cemu with --force-interpreter). In recompiler mode stack traces can not always be generated due to the way stack is managed. #641 will fix this partially

@hYdos
Copy link
Author

hYdos commented May 28, 2024

The stack trace i'm looking at is one for Cemu, not the application running. Is there a way to get one for the application or is that out of scope for Cemu?

@Exzap
Copy link
Member

Exzap commented May 28, 2024

What I said applies. It should print two stack traces, one for Cemu and another one for the PPC application running within it (if it is the PPC code that causes the crash)

@hYdos
Copy link
Author

hYdos commented Aug 1, 2024

that is not true sadly, looking at logs you get a bunch of PPC info and the Cemu Stack trace.
log.txt

@Exzap
Copy link
Member

Exzap commented Aug 1, 2024

There is a PPC stack trace and a Cemu stack trace in this log. If you update to latest Cemu then the PPC stack trace will display symbols if they are available.

@hYdos
Copy link
Author

hYdos commented Aug 3, 2024 via email

@hYdos
Copy link
Author

hYdos commented Sep 5, 2024

Cemu 2.1 has fixed SSC for some people and I happen to be one of the lucky ones. Confirmed that i get a stack trace now. However, it only works with --force-interpreter and the ui options dont' work

@hYdos hYdos changed the title Cemu crashes without a stack trace or any debugging related files Cemu crashes without a stack trace or any debugging related files when using ui to enable interpreter Sep 5, 2024
@hYdos
Copy link
Author

hYdos commented Sep 6, 2024

I wanted to update this again, Turns out Cemu does not generate a PPC stack trace when it should be all the time. It has consistently not worked the last 5 times but before that it was fine? I am able to do this using my physical WiiU but i use Cemu as a convenience tool.

@Exzap
Copy link
Member

Exzap commented Sep 6, 2024

Cemu will print a PPC stack trace if the crash actually happened during the execution of game code. If it crashes within Cemu's code it will print Not active under Active PPC instance but it should at least still print a list of all PPC threads. The relevant code is here

It would also really help if you actually posted logs and told us what you are trying to do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants