ctrl-c aborts IDL on sun? [message #38322] |
Thu, 04 March 2004 02:28  |
wmconnolley
Messages: 106 Registered: November 2000
|
Senior Member |
|
|
I'm used to using IDL on an alpha but recently forced to use a sun.
I discover that aborting a script with ctrl-c tends to kill IDL:
19 wmc@bsucena>% Interrupt encountered.
% Interrupted at: WREADU 35 /users/icd/wmc/wave/pros/wreadu.pro
% Unable to read/modify terminal characteristics.
I/O error
wmc>
Does anyone know what this means? google doesn't. If its relevant, wreadu is
in the middle of doing unformatted i/o.
-W.
--
William M Connolley | wmc@bas.ac.uk | http://www.antarctica.ac.uk/met/wmc/
Climate Modeller, British Antarctic Survey | Disclaimer: I speak for myself
I'm a .signature virus! copy me into your .signature file & help me spread!
|
|
|
|
|
|
|
|
Re: ctrl-c aborts IDL on sun? [message #38400 is a reply to message #38322] |
Thu, 04 March 2004 13:30   |
wmconnolley
Messages: 106 Registered: November 2000
|
Senior Member |
|
|
Wayne Rigby <rigby@crd.ge.com> wrote:
> This is probably of minimal use to you, but I see something
> similiar when attempting to run IDL 6.0 in 64-bit mode
> on a Sun SunBlade 150. IDL will start up, but as soon as
> you try to do just about anything, you get an error
> message and IDL hangs, e.g.
> IDL> window, 0
> % Unable to read/modify terminal characteristics.
> Bad file number
> The 32-bit version works fine on this system, and both the 32-
> and 64-bit versions work fine on a Sun Ultra.
> RSI tech support was unable to make any progress on this problem :-(
Hmm, yes, I was rather hoping for a solution, not a hint that the
problem may be rather less soluble than I feared :-(
-W.
William M Connolley | wmc@bas.ac.uk | http://www.antarctica.ac.uk/met/wmc/
Climate Modeller, British Antarctic Survey | Disclaimer: I speak for myself
I'm a .signature virus! copy me into your .signature file & help me spread!
|
|
|
|
|
|
|
Re: ctrl-c aborts IDL on sun? [message #38598 is a reply to message #38322] |
Fri, 12 March 2004 07:04  |
wmconnolley
Messages: 106 Registered: November 2000
|
Senior Member |
|
|
Stein Vidar Hagfors Haugan <steinhh@astro.uio.no> wrote:
> And I have a SunBlade 1500, not having any problem. I do remember
> having a similar problem (although without the IDL session running
> amok & eating CPU), and that problem was fixed by something related
> to the "onintr" command.... see "man onintr", and also try IDL under
> a different shell.
I did try another shell... somewhere on this thread. With bash its fine.
But thanks for your onintr - that fixes the problem too, and more
cleanly.
-W.
--
William M Connolley | wmc@bas.ac.uk | http://www.antarctica.ac.uk/met/wmc/
Climate Modeller, British Antarctic Survey | Disclaimer: I speak for myself
I'm a .signature virus! copy me into your .signature file & help me spread!
|
|
|
Re: ctrl-c aborts IDL on sun? [message #38600 is a reply to message #38443] |
Fri, 12 March 2004 06:00  |
Stein Vidar Hagfors H[2]
Messages: 28 Registered: October 2002
|
Junior Member |
|
|
"Richard G. French" <rfrench@wellesley.edu> writes:
> On 3/5/04 4:30 AM, in article 404848c1@news.nwl.ac.uk, "wmc@bas.ac.uk"
> <wmc@bas.ac.uk> wrote:
>
>> Rick Towler <rtowler@u.washington.edu> wrote:
>>> wrote in message ...
>>
>>>> I'm used to using IDL on an alpha but recently forced to use a sun.
>>
>>> I am so sorry... My thoughts are with you in this difficult time.
>>
>> Hmm. Thats not too optimistic-sounding.
>>
>>>> I discover that aborting a script with ctrl-c tends to kill IDL:
>>
>>> What version of IDL and version of Solaris?
>>
>> Sun Microsystems Inc. SunOS 5.8 Generic February 2000
>>
>> { sparc sunos unix 5.4 Sep 25 2000 32 64}
>>
>> but v6.0 has the same behaviour.
>>
>>> Can you provide a simple example?
>>
>> n fact, simply typing ctrl-c at the command prompt when nothing else
>> is happening is enough.
>>
>> wmc>
>> 57 wmc@bsucena>
>> % Interrupt encountered.
>>
>> wmc>
>> 57 wmc@bsucena>
>>
>> This doesn't generate any odd err messages, just gets me out of idl.
>> Worse, it doesn't kill the idl process - that goes mad somewhere and
>> eats the cpu. But fg doesn't work.
>>
>> -W.
>
> I have a SunBlade 1000 and ^C does not dump me out of idl
And I have a SunBlade 1500, not having any problem. I do remember
having a similar problem (although without the IDL session running
amok & eating CPU), and that problem was fixed by something related
to the "onintr" command.... see "man onintr", and also try IDL under
a different shell.
--
------------------------------------------------------------ --------------
Stein Vidar Hagfors Haugan
ESA SOHO SOC/European Space Agency Science Operations Coordinator for SOHO
NASA Goddard Space Flight Center, Tel.: 1-301-286-9028
Mail Code 682.3, Bld. 26, Room G-1, Cell: 1-240-354-6066
Greenbelt, Maryland 20771, USA. Fax: 1-301-286-0264
------------------------------------------------------------ --------------
|
|
|