I just read a message from this mailing list, that someone had problems
with STk 2.1.1 under Linux. Me too.
I verified by recompiling STk 2.1 in the same environment, that this
version works okay. With 2.1.1 I get segmentation faults.
Here is a stack trace from gdb.
(gdb) r
Starting program: /usr/src/STk-2.1.1/Src/stk-bin
Program received signal SIGSEGV, Segmentation fault.
0x600314f4 in _end ()
(gdb) bt
#0 0x600314f4 in _end ()
#1 0x1c78a0 in _end ()
#2 0x178c6 in leval (x=0xa78c4, env=0xa7b1c) at eval.c:209
#3 0x16eb4 in eval_args (l=0xa78d0, env=0xa7b1c) at eval.c:107
#4 0x181d6 in leval (x=0xa78dc, env=0xa7b1c) at eval.c:255
#5 0x18444 in leval (x=0xa7abc, env=0xa7b1c) at eval.c:279
#6 0x1bc63 in syntax_define (pform=0xbffff930, env=0x92f08) at syntax.c:320
#7 0x18147 in leval (x=0xa7a20, env=0x92f08) at eval.c:246
#8 0x715c in loadfile (fname=0xbffff95c "/usr/local/lib/stk/init.stk",
err_if_absent=1) at port.c:152
#9 0x1faa4 in load_init_file () at toplevel.c:183
#10 0x200a9 in repl_driver (argc=1, argv=0xbffffb04) at toplevel.c:287
#11 0x201c3 in toplevel (argc=1, argv=0xbffffb04) at toplevel.c:329
#12 0xf9 in main (argc=1, argv=0xbffffb04) at stk.c:30
(gdb)
--
MfG/Regards
/==== Siemens Nixdorf Informationssysteme AG
/ Ridderbusch / , Abt.: SU MR PD251
/ /./ Heinz Nixdorf Ring
/=== /,== ,===/ /,==, // W-4790 Paderborn, Germany
/ // / / // / / \ Tel.: (49) 05251-815211
/ / `==/\ / / / \ NERV:ridderbusch.pad
Email: ridderbusch.pad_at_sni-usa.com (America (North & South))
ridderbusch.pad_at_sni.de (Rest of world)
Received on Tue Aug 02 1994 - 20:24:47 CEST