Wednesday, October 31, 2018

games/ezquake and games/quakespasm broken on powerpc

Hi,

both games/ezquake and games/quakespasm won't even start. I think we should
mark them broken, but I have no idea what the issue is...

Below is a backtrace of ezquake crash and quakespasm crash log (I did not find
a .core file)


games/ezquake
-------------
Reading symbols from ezquake...(no debugging symbols found)...done.
[New process 545505]

warning: Unexpected size of section `.reg/545505' in core file.
Core was generated by `ezquake'.
Program terminated with signal SIGABRT, Aborted.

warning: Unexpected size of section `.reg/545505' in core file.
#0 0xb56d83b4 in thrkill () at {standard input}:5
5 {standard input}: No such file or directory.
(gdb) bt
#0 0xb56d83b4 in thrkill () at {standard input}:5
#1 0xb567523c in *_libc___stack_smash_handler (func=0xe38f5424 "X11_InitKeyboard", damaged=<optimized out>) at /usr/src/lib/libc/sys/stack_protector.c:79
#2 0xe38a7ae0 in X11_InitKeyboard () from /usr/local/lib/libSDL2.so.0.5
#3 0xe38af1e8 in X11_VideoInit () from /usr/local/lib/libSDL2.so.0.5
#4 0xe3896034 in SDL_VideoInit_REAL () from /usr/local/lib/libSDL2.so.0.5
#5 0xe37e9a40 in SDL_InitSubSystem_REAL () from /usr/local/lib/libSDL2.so.0.5
#6 0xe37f546c in SDL_InitSubSystem () from /usr/local/lib/libSDL2.so.0.5
#7 0x30a02424 in ?? ()
#8 0x3091f2b0 in ?? ()
#9 0x308ccb5c in ?? ()
#10 0x30a4c998 in ?? ()
#11 0x308b0264 in ?? ()
#12 0x00000000 in ?? ()


gamez/quakespasm
----------------
Command line: /usr/local/libexec/quakespasm -basedir /home/solene/quake
Found SDL version 2.0.8
Detected 1 CPUs.
Quake 1.09 (c) id Software
GLQuake 1.00 (c) id Software
FitzQuake 0.85 (c) John Fitzgibbons
FitzQuake SDL port (c) SleepwalkR, Baker
QuakeSpasm 0.93.1 (c) Ozkan Sezer, Eric Wasylishen & others
Host_Init
Playing registered version.
Console initialized.
UDP_Init: gethostbyname failed (Unknown host)
UDP Initialized
Server using protocol 666 (FitzQuake)
Exe: 13:51:42 Oct 29 2018
256.0 megabyte heap
zsh: abort quakespasm -basedir $PWD

No comments:

Post a Comment