get-internal-info problem?
I have stk-2.1.6 (with all patches I am aware of) and stk-2.2.0 (with
no patches) installed on a couple different architectures. I *think*
there was a patch of get-internal-info for 2.1.6. I recently
added some calls to get-internal-info to my code, and I started getting
intermittant seg faults, so I did some experiementation.
I ran
(dotimes (i 10000) (get-internal-info))
on various architectures with both STk versions, and here are my results.
SunOS 4.1.3_U2 Sun4m allowing dynamic loading of STk
STk-2.1.6 Core Dump - 0 times Succeed - 5 times
STk-2.2.0 Core Dump - 5 times Succeed - 0 times
SunOS 5.4 Sun4m sparc allowing dynamic loading of STk
STk-2.1.6 Core Dump - 2 times Succeed - 4 times
STk-2.2.0 Core Dump - 5 times Succeed - 0 times
Linux 1.1.54 i486, no dynamic loading for 2.1.6
allow dynamic loading for 2.2.0 using dld package
STk-2.1.6 Core Dump - 0 times Succeed - 2 times
STk-2.2.0 Core Dump - 0 times Succeed - 4 times
So, any ideas on why get-internal-info would cause segmentation faults
(and usually core dumps)?
Sarah Officer
officers_at_aries.tucson.saic.com
Received on Wed Jul 26 1995 - 18:52:44 CEST
This archive was generated by hypermail 2.3.0
: Mon Jul 21 2014 - 19:38:59 CEST