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

Segmentation Fault on GIT build #560

Closed
Enverex opened this issue May 27, 2015 · 5 comments
Closed

Segmentation Fault on GIT build #560

Enverex opened this issue May 27, 2015 · 5 comments

Comments

@Enverex
Copy link

Enverex commented May 27, 2015

Just updated and now PCSX2 instantly segfaults when trying to start (unfortunately I can't say how old the previous build from when it was working was, but I don't think it was older than a few weeks). GCC 5 being something new that stands out since the last time it was built.

I'm using Arch and the build script used to install PCSX2 is here - https://aur.archlinux.org/packages/pc/pcsx2-git/PKGBUILD (nothing special).

Dropping back to Arch's pre-packaged "pcsx2-1.3.1-2" version works fine so it looks like either something related to compilation or something in the source has changed to cause the breakage.

Relevant versions:
gcc version 5.1.0 (GCC)
kernel 4.0.4-2-ARCH

gdb doesn't provide anything useful unfortunately:

Starting program: /usr/bin/PCSX2 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x08340c46 in ?? ()

Let me know if you need anything additional.

@tiagoplacido
Copy link

Try the patch at the end of this page http://forums.pcsx2.net/Thread-SIGSEGV-with-GCC-5-0

@Enverex
Copy link
Author

Enverex commented May 27, 2015

Looks fine. Just clicked around all the different interfaces as much as possible, changing settings, etc. Nothing crashed out at any point.

@tiagoplacido
Copy link

Good, follow @gregory38 advice on that thread and see if everything works after a few days of usage

@gregory38
Copy link
Contributor

Yes. In the meantime, I will commit current patch.

gregory38 added a commit that referenced this issue May 27, 2015
Don't use const for variable object

Close issue #560
@gregory38
Copy link
Contributor

reopen the bug if you find another crash.

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

No branches or pull requests

3 participants