Ryan Freeman writes: > tested on amd64, seems to run fine, though i do get a segfault > on exit. there seems to be quite an influx of programs, games > in particular, that segfault on exit. > > (gdb) run > Starting program: /usr/local/bin/quadrupleback > seed = 1373393536 > ms-per-frame = 55 > > Program received signal SIGSEGV, Segmentation fault. > 0x000017eb54ead390 in ?? () > (gdb) bt > #0 0x000017eb54ead390 in ?? () > #1 0x000017eb60da1147 in __cxa_finalize (dso=0x0) > at /usr/src/lib/libc/stdlib/atexit.c:147 > #2 0x000017eb60d8a52a in exit (status=0) at /usr/src/lib/libc/stdlib/exit.c: > 57 > #3 0x000017e953706078 in ?? () from /usr/local/bin/quadrupleback > #4 0x0000000000000001 in ?? () > #5 0x00007f7ffffd7090 in ?? () > #6 0x0000000000000000 in ?? ()
This backtrace is not very useful without debugging symbols. Can you rebuild with DEBUG=-g and then provide a backtrace? I don't get any segfault on exit. Thanks for testing. -- Anthony J. Bentley
