If I run it first time (or after rm -rf ~/.abuse), it crashes:
[...] Engine : Registering base graphics Palette has changed, recalculating light table... white light [...................................... ] tints [.................................. ] Fatal signal: Segmentation Fault (SDL Parachute Deployed) *** glibc detected *** corrupted double-linked list: 0x00000000005b5530 *** Aborted
However, running it in gdb, it works fine, but crashes on exit:
*** glibc detected *** double free or corruption (!prev): 0x00000000005b5540 ***
Program received signal SIGABRT, Aborted. 0x00002aaaabffc11d in raise () from /lib/libc.so.6
After one time running it in gdb, it works the same every time after, no matter whether it runs in gdb or not: it works fine, but crashes on exit.
Maybe the "darkness calibration" and/or the writing of config files is at fault?
If I run it first time (or after rm -rf ~/.abuse), it crashes:
[...] ....... ....... ....... ....... .... ] ....... ....... ....... ....... ]
Engine : Registering base graphics
Palette has changed, recalculating light table...
white light [......
tints [......
Fatal signal: Segmentation Fault (SDL Parachute Deployed)
*** glibc detected *** corrupted double-linked list: 0x00000000005b5530 ***
Aborted
However, running it in gdb, it works fine, but crashes on exit:
*** glibc detected *** double free or corruption (!prev): 0x00000000005b5540 ***
Program received signal SIGABRT, Aborted.
0x00002aaaabffc11d in raise () from /lib/libc.so.6
After one time running it in gdb, it works the same every time after, no matter whether it runs in gdb or not: it works fine, but crashes on exit.
Maybe the "darkness calibration" and/or the writing of config files is at fault?