Fwd: SDL2 applications crashing with SIGBUS

Elias Bürli <[email protected]>
Newsgroups gmane.os.netbsd.ports.sparc64
Message-ID <CAK2Gejks1hy2bUF1GxUqrOhceYN20d3+rF8baM6T6FWSYjadMg@mail.gmail.com>
edit: forgot to include [email protected] in CC

Hello

For tyr-quake, I tried the pre-compiled package here:
ftp://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/games/tyrquake/README.html
which also needs at least the shareware data:
ftp://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/games/quakedata/README.html
It successfully shows the splash screen, and if I hit ESC fast enough
I can get into the menu, but it crashes when trying to start a new
game.

Chocolate-Doom I compiled from source (chocolate-doom-3.0.0.tar.gz),
"./configure", "make", and "make install" worked without issues.
https://www.chocolate-doom.org/wiki/index.php/Downloads
Also requires game data:
ftp://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/games/doom1/README.html

Dune Legacy I also compiled from source (dunelegacy-0.96.4-src.tar.bz2 )
http://dunelegacy.sourceforge.net/website/downloads.html
Also requires original game data, but is not freely available.

I was also expecting the issue to be in the game source itself, which
is why I find the gdb reference to "XkbSetDetectableAutoRepeat () from
/usr/pkg/lib/libX11.so.6" confusing.

Best regards
Elias

On Mon, Jan 21, 2019 at 5:34 PM Martin Husemann <[email protected]> wrote:
>
> On Mon, Jan 21, 2019 at 05:23:19PM +0100, Elias Bürli wrote:
> > Hello
> >
> > I'm using the sparc64 port of NetBSD 8.0 on my Sun Ultra 10 with a
> > Creator3D card. The system itself is running fine.
> > But when I wanted to try out some SDL2-based games compiled from
> > source, I'm only getting SIGBUS crashes (probably due to some
> > unaligned memory access).
>
> Can you give an example of such a game (preferably small and from pkgsrc)?
> This usually is an issue in the application (or maybe SDL in this case).
>
> Martin
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.