Subj : Segment Fault with the latest mystic v1.12 A47 Release
To   : g00r00
From : Bj”rn Wiberg
Date : Sun Aug 15 2021 09:36 am

Hello g00r00!

On 14 Aug 2021, g00r00 said the following...
 g0> I don't seem to be able to reproduce this here on Ubuntu 20 64-bit with
 g0> the  latest A47.  I wonder what could be different?  I'll make a new
 g0> build since I have that filename change for the View anyway for you to
 g0> test... Let me know if
 g0> it still happens in the latest build.

Unfortunately, yes -- same error message...

Tried some gdb but doesn't have any symbols, so no good references to
anything there, I think?

bbs@glimmer:~/mystic$ gdb -ex=r --args /home/bbs/mystic/mystic -cfg

(pressing N and then R)

Thread 1 "mystic" received signal SIGSEGV, Segmentation fault.
                                                              0x0000000000460f5d in ?? ()
(gdb) bt full
#0  0x0000000000460f5d in ?? ()
No symbol table info available.
#1  0x00007fffffff3850 in ?? ()
No symbol table info available.
#2  0x000000000063aba0 in ?? ()
No symbol table info available.
#3  0x0000000000000000 in ?? ()
No symbol table info available.
(gdb) quit
A debugging session is active.

        Inferior 1 [process 7929] will be killed.

Quit anyway? (y or n) y

Not sure how to proceed in the best way...

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/14 (Linux/64)
 * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

.