#683054 /usr/games/torus-trooper-pure: torus-trooper(-pure) segfaults at startup on armhf

#683054#5
Date:
2012-07-28 07:42:46 UTC
From:
To:
torus-trooper and torus-trooper-pure segfaults on my Toshiba AC100
running Debian armhf. It runs fine on my computer running amd64 so it
might be architecture specific. Here is the stacktrace I could gather:

(gdb) run
Starting program: /usr/games/torus-trooper-pure
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/arm-linux-gnueabihf/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00026d10 in gcc.deh.personalityImpl() ()
(gdb) bt
#0  0x00026d10 in gcc.deh.personalityImpl() ()
#1  0x00026d4c in __gdc_personality_v0 ()
#2  0x402cdc22 in ?? () from /lib/arm-linux-gnueabihf/libgcc_s.so.1
#3  0x402ce43e in _Unwind_RaiseException () from
/lib/arm-linux-gnueabihf/libgcc_s.so.1
#4  0x00026dc6 in _d_throw ()
#5  0x00035122 in std.stream.File.open() ()
#6  0x000249a0 in abagames.util.tokenizer.Tokenizer.readFile()
(fileName=..., separator=...) at src-hiz/abagames/util/tokenizer.d:20
#7  0x00013ca2 in abagames.tt.boot.readOptionsIniFile() () at
src-hiz/abagames/tt/boot.d:167
#8  0x00013cd2 in abagames.tt.boot.parseArgs() (commandArgs=...) at
src-hiz/abagames/tt/boot.d:96
#9  0x00014090 in abagames.tt.boot.boot() (args=...) at
src-hiz/abagames/tt/boot.d:80
#10 0x00042a52 in dgccmain2._d_run_main() ()
#11 0x00042aa4 in _d_run_main ()
#12 0x402eecfa in __libc_start_main (main=0x4093d <main+1>, argc=1,
ubp_av=0xbe834794, init=<optimized out>,
    fini=0x42d41 <__libc_csu_fini+1>, rtld_fini=0x40045f49 <_dl_fini>,
    stack_end=0xbe834794) at libc-start.c:228
    #13 0x0000cdce in _start ()

It tries to open options.ini and then for some reason there is an
exception launched and the unwind associated fails. Maybe the bug is in
libgcc_s...

Best regards.

Thomas Preud'homme

#683054#14
Date:
2013-04-16 13:50:04 UTC
From:
To:
Le samedi 28 juillet 2012 09:42:46, Thomas Preud'homme a écrit :

Since I don't have hardware acceleration on that laptop I suppose the bug come
from here. I'm just surprised a SEGFAULT happens instead of just an error but
you can close the bug if you feel it's not a problem.

Best regards,

Thomas