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

Home » Public Forums » archive » Re: path_sep() or where() crashing my idlde
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: path_sep() or where() crashing my idlde [message #36830 is a reply to message #36829] Sun, 02 November 2003 01:02 Go to previous messageGo to previous message
Paul Sorenson is currently offline  Paul Sorenson
Messages: 48
Registered: May 2002
Member
It used to be that IDL would remember accross sessions commands that had
been issued at the IDL prompt. For example, you could fire up a fresh
instance of IDL, hit up-arrow, and see the last command you had entered the
previous time you were running IDL! I don't know if this is still the case,
and I think it worked only on Macs. Also, I don't know where that
information is or was stored.

Have you tried re-installing IDL?

-Paul Sorenson

"Thomas Brueckner" <profxtjb@earthlink.net> wrote in message
news:52e94d00.0311012322.72bb4343@posting.google.com...
> David Fanning <david@dfanning.com> wrote in message news:
>
>> I know the Mac versions of IDL tend to store information
>> from one IDL session to the other. I don't know off-hand
>> where this information is stored, but I'd try to find out
>
> As near as I can figure the data is stored in .idlde and all of it is
> preferences and lists of recent files etc.
>
>
> Here is part of the idlde.crash.log from this morning:
>
> Date/Time: 2003-10-31 11:21:24 -0500
> OS Version: 10.3 (Build 7B85)
>
> Command: idlde (/usr/local/rsi/idl_6.0/bin/bin.darwin.ppc/idlde)
> PID: 894
> Thread: 0
>
> Exception: EXC_BAD_INSTRUCTION (0x0002)
> Code[0]: 0x00000002
> Code[1]: 0x01aceb64
>
>
> Thread 0 Crashed:
> #0 0x01aceb64 in IDL_where (IDL_where + 576)
> #1 0x01a1bed0 in interpreter (interpreter + 13936)
> #2 0x01b932bc in IDL_Executive (IDL_Executive + 3504)
> #3 0x01a20690 in IDL_InterpCallFromSysproc
> (IDL_InterpCallFromSysproc + 204)
> #4 0x01ad21e4 in call_user_cb (call_user_cb + 140)
> #5 0x01ad95a4 in internal_widget_event (internal_widget_event +
> 2208)
> #6 0x01ad9734 in IDL_widget_event (IDL_widget_event + 52)
> #7 0x01a1bed0 in interpreter (interpreter + 13936)
> #8 0x01b932bc in IDL_Executive (IDL_Executive + 3504)
> #9 0x01774464 in IDL_Main (IDL_Main + 136)
> #10 0x00002808 in main (main + 1136)
> #11 0x000022e4 in _start (_start + 460)
> #12 0x00002114 in start (start + 48)
>
>
>
>
>
>
> And here is a similar portion of idl.crash.log:
>
> Date/Time: 2003-11-01 04:12:54 -0500
> OS Version: 10.3 (Build 7B85)
>
> Command: idl (/usr/local/rsi/idl_6.0/bin/bin.darwin.ppc/idl)
> PID: 526
> Thread: 0
>
> Exception: EXC_BAD_INSTRUCTION (0x0002)
> Code[0]: 0x00000002
> Code[1]: 0x01aceb64
>
>
> Thread 0 Crashed:
> #0 0x01aceb64 in IDL_where (IDL_where + 576)
> #1 0x01a1bed0 in interpreter (interpreter + 13936)
> #2 0x01b932bc in IDL_Executive (IDL_Executive + 3504)
> #3 0x01774464 in IDL_Main (IDL_Main + 136)
> #4 0x00002808 in main (main + 1136)
> #5 0x000022e4 in _start (_start + 460)
> #6 0x00002114 in start (start + 48)
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: 2D scatter plot with density contour line,
Next Topic: Re: access to vercities & connectivity data

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

Current Time: Fri Oct 10 14:35:25 PDT 2025

Total time taken to generate the page: 0.32136 seconds