-
-
Notifications
You must be signed in to change notification settings - Fork 712
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
Linux - Segmentation fault on latest commit #568
Comments
If you have the time, please test a few commits past the 2.0 release commit (da9b26f). You can go back with |
Sorry for the late response, I updated Fedora yesterday and it's having some teething issues, mainly Vulkan related. I tried compiling the commit you recommended and it suffered the exact same segfault, so I'm thinking there must be something with one of the dependent packages in the Fedora repo, but as the debugging info isn't helpful at all I would't know where to start. Thank you for responding. |
I am also having similar issues. I am using gcc-14 built from source, on Ubuntu 22.04.4 LTS. I am looking in tracking down the issue, but it could be something with glibc. Not sure if this is 100% related or not, but this is the log I'm getting crashing in a similar location Loaded '/usr/local/lib64/libstdc++.so.6'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libm.so.6'. Symbols loaded.
Loaded '/usr/local/lib64/libgcc_s.so.1'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libc.so.6'. Symbols loaded.
[New Thread 0x7ffff203e640 (LWP 17983)]
Thread 3 "shadPS4:Log" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff203e640 (LWP 17983)]
std::__new_allocator<char>::allocate (this=0x7ffff203dab0, __n=80) at /usr/local/include/c++/14.2.0/bits/new_allocator.h:151
151 return static_cast<_Tp*>(_GLIBCXX_OPERATOR_NEW(__n * sizeof(_Tp)));
Execute debugger commands using "-exec <command>", for example "-exec info registers" will list registers in use (when GDB is the debugger)
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 17977) killed] Looking at the call stack, this is the last shadPS4 location: |
I can get past the colored terminal segfault by checking "Emulate terminal in the output console" in CLion, but then I crash trying to mmap: shadPS4/src/core/address_space.cpp Line 311 in 1651db2
|
#663 is able to run the OpenOrbis samples and Sonic Mania on my end, so the issue may be fixed now. @kiwidoggie and @NotNite if you wouldn't mind building it and reporting your experiences that would be great. Also, this commit manages to show the company logos in The Last Guardian (1.0, 1.3 instantly crashes), so that's progress that has me excited. |
Can't even compile it anymore since recent commits,
|
Thanks for the heads up! I launched a random game (P.T. CUSA01127) and it crashed immediately,
Should I open a new bug report, or that seems to be normal? I will retry on wine with a Windows build later on. |
can't build since recent commits (haven't checked from exactly which yet):
|
Hi ShadPS4 Devs
I just built the latest commit under Fedora 40 following the build instructions in the repo and it just immediately segfaults upon execution, recompiling it with the debug flag and running in gdb prints the following output:
Running the release build (0.2.0) works fine.
It's not much to go on so I don't know if it'll be of any use, but I hope it helps. Thanks for taking the time to give this a look.
The text was updated successfully, but these errors were encountered: