Segmentation fault (core dumped)

[osiriswrecks]

I built GSPlus from source on my Fedora laptop and tried running ./gsplusx in it's own folder, but got a segmentation fault. Not sure if it's an issue on my system or in the code, but nothing I've Googled has helped. Any ideas what could be causing this? Full output:

Trying 'config.txt'
Parsing configuration file
Read: 262144 bytes of ROM
Patching ROM 03 smartport bug
RAM size is 0 - 900000 (9.00MB)
Preparing X Windows graphics system
Visual 0
    id: 00000020, screen: 0, depth: 24, class: 4
    red: 00ff0000, green: 0000ff00, blue: 000000ff
    cmap size: 256, bits_per_rgb: 8
Chose visual: 0, max_colors: -1
Will use shared memory for X
Segmentation fault (core dumped)

[osiriswrecks]

For a frame of reference, I compiled the source in an Ubuntu VM and it loads the X11 window perfectly fine after running "./gsplusx". I will try it on my more powerful Fedora rig as well to see if it's specific to that particular laptop I was using.

EDIT: Nope, it doesn't work on my beefy Fedora rig either. Seems to be distro-specific?

[digarok]

The X11 version is largely deprecated as I've focused on doing a single abstraction via SDL2 for now. That said, I still try to maintain the Makefile and my CI builds still always check X11 on Ubuntu.

I'm guessing it's a small library difference in Fedora in this case. I'll see if I can get a test VM running for Fedora and take a look at this.

[osiriswrecks]

I’m happy to test on my end, too - I’m still running Fedora on bare metal so I can pull stuff down and try to build it on my side. Thanks for looking into it!

On Dec 29, 2017, at 9:57 AM, Dagen Brock [email protected] wrote:

The X11 version is largely deprecated as I've focused on doing a single abstraction via SDL2 for now. That said, I still try to maintain the Makefile and my CI builds still always check X11 on Ubuntu.

I'm guessing it's a small library difference in Fedora in this case. I'll see if I can get a test VM running for Fedora and take a look at this.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.