comp.lang.idl-pvwave archive: archive » Re: path_sep() or where() crashing my idlde

Home » Public Forums » archive » Re: path_sep() or where() crashing my idlde

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: path_sep() or where() crashing my idlde [message #36822]

Mon, 03 November 2003 06:10

btt
Messages: 345
Registered: December 2000

Senior Member

David Fanning wrote:
> Thomas Brueckner writes:
>
>
>> For some reason, path_sep() is crashing my idlde. I am running IDL
>> 6.0 for evaluation, with
>> !version.os_family = 'unix' on a Mac G4.
>>
>> I would love to know why the where() function is causing this trouble
>> and how to fix it.
>
>
> I seriously doubt the WHERE function (my vote for *the*
> most useful function in IDL) is causing this trouble.
> More likely a problem with the a path variable, or something
> of that sort.
>
> 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
> and delete the file, so you can start over from scratch.
> I'm pretty sure if you did that the WHERE function would
> be miraculously restored. :-)
>
> Best Regards,
>
> David
>
> P.S. I'm counting on the Mac guys to tell us what
> needs to be deleted here. I'm sure they all have
> experience. :-)
>
Hi,

The behavior you describe, David, certainly was true for macOS9 which had a very
nice IDLDE. In MacOS9 the was a problem with accumulating files in a temporary
directory; I recall haviung to manually search for and delete these (mostly)
hidden files. But in OSX with IDL6.0 I never see that memory behavior between
sessions (I haven't seen a very nice IDLDE either!)

I just tried the following without a problem.

IDL> print, !version
{ ppc darwin unix Mac OS X 6.0 Jun 27 2003 32 32}
IDL> print, path_sep()
/

Ben

Report message to a moderator

Re: path_sep() or where() crashing my idlde [message #36829 is a reply to message #36822]

Sun, 02 November 2003 06:19

profxtjb
Messages: 22
Registered: October 2003

Junior Member

"Paul Sorenson" <aardvark62@msn.com> wrote in message news:<3fa4c826_5@127.0.0.1>...

> Have you tried re-installing IDL?

I was going to wait a while longer before doing a re-install. I want
to learn whether I can get this solved without dropping the re-install
bomb. Whatever I learn is beneficial.

Those crash logs look grim, but maybe someone in RSI will see them and
be able to make sense of them. That is my hope.

==thomas==

Report message to a moderator

Re: path_sep() or where() crashing my idlde [message #36830 is a reply to message #36829]

Sun, 02 November 2003 01:02

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)

Report message to a moderator

Re: path_sep() or where() crashing my idlde [message #36831 is a reply to message #36830]

Sat, 01 November 2003 23:22

profxtjb
Messages: 22
Registered: October 2003

Junior Member

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)

Report message to a moderator

Re: path_sep() or where() crashing my idlde [message #36841 is a reply to message #36831]

Sat, 01 November 2003 07:48

David Fanning
Messages: 11724
Registered: August 2001

Senior Member

Thomas Brueckner writes:

> For some reason, path_sep() is crashing my idlde. I am running IDL
> 6.0 for evaluation, with
> !version.os_family = 'unix' on a Mac G4.
>
> I would love to know why the where() function is causing this trouble
> and how to fix it.

I seriously doubt the WHERE function (my vote for *the*
most useful function in IDL) is causing this trouble.
More likely a problem with the a path variable, or something
of that sort.

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
and delete the file, so you can start over from scratch.
I'm pretty sure if you did that the WHERE function would
be miraculously restored. :-)

Best Regards,

David

P.S. I'm counting on the Mac guys to tell us what
needs to be deleted here. I'm sure they all have
experience. :-)

--
David W. Fanning, Ph.D.
Fanning Software Consulting, Inc.
Phone: 970-221-0438, E-mail: david@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155

Report message to a moderator

Re: path_sep() or where() crashing my idlde [message #36918 is a reply to message #36822]

Mon, 03 November 2003 10:22

profxtjb
Messages: 22
Registered: October 2003

Junior Member

Ben Tupper <btupper@bigelow.org> wrote in message news:<bo5nkj$17nh7h$1@ID-189398.news.uni-berlin.de>...> I just tried the following without a problem.
>
> IDL> print, !version
> { ppc darwin unix Mac OS X 6.0 Jun 27 2003 32 32}
> IDL> print, path_sep()
> /

Ben, here is what my IDL does:

IDL> print, path_sep()
% Compiled module: PATH_SEP.
Illegal instruction

Then it exits to the shell. Seems crazy that this should be faulty.

Report message to a moderator

Re: path_sep() or where() crashing my idlde [message #36965 is a reply to message #36830]

Wed, 12 November 2003 04:41

profxtjb
Messages: 22
Registered: October 2003

Junior Member

"Paul Sorenson" <aardvark62@msn.com> wrote in message news:<3fa4c826_5@127.0.0.1>...
> 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?

CONCLUSION:

No other help or insight was forthcoming. I did re-install last week.

Thanks to everybody who contributed.

==thomas==

Report message to a moderator

Previous Topic:	2D scatter plot with density contour line,
Next Topic:	Re: access to vercities & connectivity data

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 14:55:52 PDT 2025

Total time taken to generate the page: 0.00500 seconds