| Re: external c shared libraries [message #16580] |
Fri, 06 August 1999 00:00 |
Haje Korth
Messages: 651
Registered: May 1997
|
Senior Member |
|
|
David,
Note of sympathy: I have the same problem on the Sun version and I haven't
found a way around it. A few time I crashed the workstation completely by
recompiling while IDL and the library being active.
Regards,
Haje
"D. Mattes" wrote:
> hello IDL gurus: i have a couple questions re: calling external c
> functions from IDL. platform: unix OSF/1, version: IDL 5.2
>
> 1) in doing development, debugging, etc. i notice that once the shared
> library is changed (recompiled), IDL will crash and burn if i try and
> access the changed shared lib. i can understand this happening, but is
> there a way to prevent this?
--
------------------------------------------------------------ ----------------
Haje Korth
Space and Atmospheric Sciences (NIS-1)
MS D466
Los Alamos National Laboratory
Los Alamos, NM 87545
Phone: (505) 667-0788
FAX: (505) 665-7395
e-mail: hkorth@lanl.gov
------------------------------------------------------------ ----------------
|
|
|
|
| Re: external c shared libraries [message #16593 is a reply to message #16580] |
Fri, 06 August 1999 00:00  |
Nando Iavarone
Messages: 48
Registered: December 1998
|
Member |
|
|
<HTML>
D. Mattes wrote:
<BLOCKQUOTE TYPE=CITE>2) my shared library function returns the correct
values into IDL, but
<BR>then a few moments later, as IDL is waiting statically for user input,
IDL
<BR>will just seem to spontaneously crash. why? mind you, this
only occurs
<BR>with IDLDE. with the line command version IDL, i never get a
crash.</BLOCKQUOTE>
I had the same problem when in the external code I used string,and I forgot
to close them (\0 terminator) in the string structure of IDL.
<BR>But the crash was not prevedible (i.e.: you can use the string in IDL
and to see it ok,
<BR>but another parameter is corrupted).
<BR>have you the external code of the function you call from IDL?
<P>warn us if you find the problem and the solution.
<BR>ciao.
<PRE>--
Nando Iavarone
Advanced Computer System - SPACE DIVISION
via Lazzaro Belli, 23
00040 Frascati - RM
Tel: +39-6-944091 (switchboard)
9440968 (direct)
E-mail:
f.iavarone@acsys.it
FrdndVrn@altavista.net</PRE>
</HTML>
|
|
|
|
| Re: external c shared libraries [message #16601 is a reply to message #16580] |
Thu, 05 August 1999 00:00 |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
D. Mattes (dmattes@u.washington.edu) writes:
> 1) in doing development, debugging, etc. i notice that once the shared
> library is changed (recompiled), IDL will crash and burn if i try and
> access the changed shared lib. i can understand this happening, but is
> there a way to prevent this?
Not currently. But I hear totally unsubstantiated rumors that
the times, they are a changin'. :-)
> 2) my shared library function returns the correct values into IDL, but
> then a few moments later, as IDL is waiting statically for user input, IDL
> will just seem to spontaneously crash. why? mind you, this only occurs
> with IDLDE. with the line command version IDL, i never get a crash.
Don't know. You getting some kind of error message, or
IDL just folds up its tents and goes home?
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438 E-Mail: davidf@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
