Dear Olin,
I have reported some time ago that scsh dumps core under solaris-2.3 on
"(date)". In the meantime I upgraded the system to Solaris-2.4 and I
have just discovered that this time "(date)" returns the correct result,
i.e., the date-record '#{%date}, e.g.,
> (date->string (date))
"Fri Jun 23 16:36:13 1995"
>
I have also tried to load slib2a2, but that attempt resulted in the core dump:
gustav@jupiter:~ 378 $ scsh
Scsh 0.3
> (load "/opt/gnu/lib/scm/scheme48.init")
/opt/gnu/lib/scm/scheme48.init
......................................../opt/gnu/lib/scm/slib/req
uire.scm .......................Segmentation Fault (core dumped)
gustav@jupiter:~ 379 $ dbx /opt/gnu/lib/scsh/scshvm core
Reading symbolic information for /opt/gnu/lib/scsh/scshvm
corefile read successfully
Reading symbolic information for rtld /usr/lib/ld.so.1
Reading symbolic information for /usr/lib/libm.so.1
Reading symbolic information for /usr/lib/libdl.so.1
Reading symbolic information for /usr/lib/libnsl.so.1
Reading symbolic information for /usr/lib/libsocket.so.1
Reading symbolic information for /usr/lib/libelf.so.1
Reading symbolic information for /usr/lib/libc.so.1
Reading symbolic information for /usr/lib/libintl.so.1
Reading symbolic information for /usr/lib/libw.so.1
program terminated by signal SEGV (segmentation violation)
(dbx) where
Tinterpret(0, 0xffde8c62, 0x1, 0x1, 0, 0) at 0x17a80
TTrun_machine(0x17a58, 0xfffffff8, 0x20ce0, 0x38400, 0x5f40f8,
0x38400) at 0x15f3c
call_startup_procedure(0x38b27, 0xeffff8b8, 0, 0x9c4, 0x2d,
0x5c) at 0x1d638
main(0x38ac0, 0xeffff8b8, 0xeffff8bc, 0x3843c, 0, 0) at 0x15608
(dbx)
Should I be able to load slib at all under scsh?
Best regards and greetings from Down Under,
Zdzislaw Meglicki, Zdzislaw.Meglicki@cisr.anu.edu.au,
Parallel Computing Research Facility, CISR,
The Australian National University, Canberra, A.C.T., 0200,
Australia, fax: +61-6-249-0747, tel: +61-6-249-0158
|