comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Problem using sav files.
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Problem using sav files. [message #21794] Thu, 21 September 2000 00:00 Go to next message
Theo Brauers is currently offline  Theo Brauers
Messages: 58
Registered: November 1997
Member
Hi experts:

I am stuck with a problem using a sav file:

My program is an widget driven i/o interface for FACSIMILE. It
consists of about 400 functions/routines. When I compile the
whole thing using resolve_all it works fine in this IDL session.
However, when I save the thing ( easy.sav ) and restart IDL using
the easy.sav file it worked fine for a while, then the thing
crashes IDL totally during operation even when I use the same
input data. Restarting IDL with sav file: crash. Restarting
IDL with source compiled: OK. Save and restart: Crash. Rebooting
and repeating gives the same result. I can also reproduce this
behaviour on a different machine, with different user profile.
I had the same behaviour with a previous version of the program
which crashed in the same way at a different location in the
program but I cannot reproduce this again :-|

Does anybody have similar problems? Is there any possibility
to catch an error before IDL crashes?
I am using: { x86 Win32 Windows 5.3.1 Feb 23 2000}

Best regards

Theo



--
----------------------------------------------
Dr. Theo Brauers
Institut fuer Atmosphaerische Chemie (ICG-3)
Forschungszentrum Juelich
52425 JUELICH, Germany
Tel. +49-2461-61-6646 Fax. +49-2461-61-5346
http://www.kfa-juelich.de/icg/icg3/MITARBEITER/th.brauers.ht ml
Re: Problem using sav files. [message #21871 is a reply to message #21794] Fri, 22 September 2000 00:00 Go to previous messageGo to next message
promashkin is currently offline  promashkin
Messages: 169
Registered: December 1999
Senior Member
I would not expect 5.4 to solve this. I was able so far to use restored
routines just as fine as compiled ones in 5.3 and would not be surprised
if the problem carriad over into 5.4. I think it needs to be tracked down.
Leave it alone for a while. At a later time, it might become obvious why
did it do this. This approach worked for me a couple of times.
Cheers,
Pavel
Re: Problem using sav files. [message #21874 is a reply to message #21794] Fri, 22 September 2000 00:00 Go to previous messageGo to next message
Theo Brauers is currently offline  Theo Brauers
Messages: 58
Registered: November 1997
Member
Liam Gumley wrote:
>
>
> The next step would be to reproduce the problem with the fewest lines of
> code.
>
> Cheers,
> Liam.
>
Sounds like hours or days of work. I'll sneak off .......... friday 4:30pm,
weekend, .... When does IDL 5.4 (not beta) show up?

Thanks for your help.

Theo
Re: Problem using sav files. [message #21945 is a reply to message #21794] Thu, 05 October 2000 00:00 Go to previous message
Theo Brauers is currently offline  Theo Brauers
Messages: 58
Registered: November 1997
Member
Theo Brauers wrote:
>
> Hi experts:
>
> I am stuck with a problem using a sav file:
>
> My program is an widget driven i/o interface for FACSIMILE. It
> consists of about 400 functions/routines. When I compile the
> whole thing using resolve_all it works fine in this IDL session.
> However, when I save the thing ( easy.sav ) and restart IDL using
> the easy.sav file it worked fine for a while, then the thing
> crashes IDL totally during operation even when I use the same
> input data. Restarting IDL with sav file: crash. Restarting
> IDL with source compiled: OK. Save and restart: Crash. Rebooting
> and repeating gives the same result. I can also reproduce this
> behaviour on a different machine, with different user profile.
> I had the same behaviour with a previous version of the program
> which crashed in the same way at a different location in the
> program but I cannot reproduce this again :-|
>
> Does anybody have similar problems? Is there any possibility
> to catch an error before IDL crashes?
> I am using: { x86 Win32 Windows 5.3.1 Feb 23 2000}
>
> Best regards
>
> Theo
>
Problem solved! Thanks to all contributors and to Reimar
Bauer. :-)

What was wrong? We use an external routine (dll using fstat)
determining the modification date of files. When we called
this routine with a not existing filename IDL crashes.
However, the reason for invalid filenames was the
HELP, CALL=c procedure giving different results when called
from compiled code or from a sav file.

Try this one:
;- test2.pro ------------
FUNCTION testfunc
HELP, CALL=c
r = DIALOG_MESSAGE(c, /INFO)
RETURN, c
END

PRO test2
c = testfunc()
END
-------------

IDL> .COMPILE test2
IDL> test2
IDL> SAVE, /ROUT, FILE='test2.sav'
IDL> RESTORE, /ROUT, FILE='test2.sav'
IDL> test2

Showing me that SAVE and RESTORE do not exactly restore the
previous session.

Best Theo
Re: Problem using sav files. [message #21952 is a reply to message #21794] Wed, 04 October 2000 00:00 Go to previous message
R.Bauer is currently offline  R.Bauer
Messages: 1424
Registered: November 1998
Senior Member
Theo Brauers wrote:
>
> Hi experts:
>
> I am stuck with a problem using a sav file:
>
> My program is an widget driven i/o interface for FACSIMILE. It
> consists of about 400 functions/routines. When I compile the
> whole thing using resolve_all it works fine in this IDL session.
> However, when I save the thing ( easy.sav ) and restart IDL using


...

Some routines gave different results in runtime specially
HELP,CALL=CALL

In development it returns the filename and its location.
During runtime it's the uppercased routine name.

If this is used as input to another routine it is possible thats
an empty string is passed.



regards
Reimar
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: How can I change the color of a WIDGET_BASE?
Next Topic: camera object?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 15:26:42 PDT 2025

Total time taken to generate the page: 0.33782 seconds