| Mystical IDL_IDLBridge error [message #89412] |
Mon, 13 October 2014 11:55  |
cgguido
Messages: 195
Registered: August 2005
|
Senior Member |
|
|
On some of my machines, I cannot get the bridge to work. The error message is mystical and I have no idea how to dig deeper ... Any tips?
Thanks,
G
I cannot get this to
IDL> print, !version
{ x86_64 darwin unix Mac OS X 7.1.1 Aug 19 2009 64 64}
IDL> a=obj_new('idl_idlbridge')
% Loaded DLM: IDL_IDLBRIDGE.
% Unable to start IDL_IDLBRIDGE slave process.
% Execution halted at: $MAIN$
IDL> print, !version
{ x86_64 darwin unix Mac OS X 8.1 Mar 9 2011 64 64}
IDL> a=obj_new('idl_idlbridge')
% Loaded DLM: IDL_IDLBRIDGE.
% Unable to start IDL_IDLBRIDGE slave process.
% Execution halted at: $MAIN$
|
|
|
|
|
|
| Re: Mystical IDL_IDLBridge error [message #89417 is a reply to message #89414] |
Tue, 14 October 2014 10:54  |
cgguido
Messages: 195
Registered: August 2005
|
Senior Member |
|
|
Merci Antoine,
but that was not the problem. No zombie IDL process and a restart does not solve it either...
I am wondering if there is a way to make obj_new() more verbose... or maybe there is a way to call the idl_idlbridge dll from somewhere else.... just a way to get more info on what's failing....
G
On Tuesday, October 14, 2014 4:01:15 AM UTC-5, Antoine Cottin wrote:
> Hi Gianguido,
>
>
>
> I had in the past some similar message.
>
> Did restarting your computer solve this kind of issue... if so it certainly means that you have IDL processes still run/idlde in the background... sometimes IDL is not able to kill some IDL_Bridge process, it's a known bug under Linux and Os X.
>
>
>
> I solved it by going into the Activity Monitor and manually killed remaining IDL processes...
>
>
>
> Cheers
>
> Antoine
>
>
>
>
>
> Le lundi 13 octobre 2014 19:55:45 UTC+1, Gianguido Cianci a écrit :
>
>> On some of my machines, I cannot get the bridge to work. The error message is mystical and I have no idea how to dig deeper ... Any tips?
>
>>
>
>>
>
>>
>
>> Thanks,
>
>>
>
>> G
>
>>
>
>>
>
>>
>
>> I cannot get this to
>
>>
>
>> IDL> print, !version
>
>>
>
>> { x86_64 darwin unix Mac OS X 7.1.1 Aug 19 2009 64 64}
>
>>
>
>> IDL> a=obj_new('idl_idlbridge')
>
>>
>
>> % Loaded DLM: IDL_IDLBRIDGE.
>
>>
>
>> % Unable to start IDL_IDLBRIDGE slave process.
>
>>
>
>> % Execution halted at: $MAIN$
>
>>
>
>>
>
>>
>
>>
>
>>
>
>> IDL> print, !version
>
>>
>
>> { x86_64 darwin unix Mac OS X 8.1 Mar 9 2011 64 64}
>
>>
>
>> IDL> a=obj_new('idl_idlbridge')
>
>>
>
>> % Loaded DLM: IDL_IDLBRIDGE.
>
>>
>
>> % Unable to start IDL_IDLBRIDGE slave process.
>
>>
>
>> % Execution halted at: $MAIN$
|
|
|
|
| Re: Mystical IDL_IDLBridge error [message #89418 is a reply to message #89417] |
Tue, 14 October 2014 13:14 |
chris_torrence@NOSPAM
Messages: 528
Registered: March 2007
|
Senior Member |
|
|
On Tuesday, October 14, 2014 11:54:18 AM UTC-6, Gianguido Cianci wrote:
> Merci Antoine,
>
>
>
> but that was not the problem. No zombie IDL process and a restart does not solve it either...
>
> I am wondering if there is a way to make obj_new() more verbose... or maybe there is a way to call the idl_idlbridge dll from somewhere else.... just a way to get more info on what's failing....
>
>
>
> G
>
>
>
>
>
>
>
> On Tuesday, October 14, 2014 4:01:15 AM UTC-5, Antoine Cottin wrote:
>
>> Hi Gianguido,
>
>>
>
>>
>
>>
>
>> I had in the past some similar message.
>
>>
>
>> Did restarting your computer solve this kind of issue... if so it certainly means that you have IDL processes still run/idlde in the background... sometimes IDL is not able to kill some IDL_Bridge process, it's a known bug under Linux and Os X.
>
>>
>
>>
>
>>
>
>> I solved it by going into the Activity Monitor and manually killed remaining IDL processes...
>
>>
>
>>
>
>>
>
>> Cheers
>
>>
>
>> Antoine
>
>>
>
>>
>
>>
>
>>
>
>>
>
>> Le lundi 13 octobre 2014 19:55:45 UTC+1, Gianguido Cianci a écrit :
>
>>
>
>>> On some of my machines, I cannot get the bridge to work. The error message is mystical and I have no idea how to dig deeper ... Any tips?
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> Thanks,
>
>>
>
>>>
>
>>
>
>>> G
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> I cannot get this to
>
>>
>
>>>
>
>>
>
>>> IDL> print, !version
>
>>
>
>>>
>
>>
>
>>> { x86_64 darwin unix Mac OS X 7.1.1 Aug 19 2009 64 64}
>
>>
>
>>>
>
>>
>
>>> IDL> a=obj_new('idl_idlbridge')
>
>>
>
>>>
>
>>
>
>>> % Loaded DLM: IDL_IDLBRIDGE.
>
>>
>
>>>
>
>>
>
>>> % Unable to start IDL_IDLBRIDGE slave process.
>
>>
>
>>>
>
>>
>
>>> % Execution halted at: $MAIN$
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> IDL> print, !version
>
>>
>
>>>
>
>>
>
>>> { x86_64 darwin unix Mac OS X 8.1 Mar 9 2011 64 64}
>
>>
>
>>>
>
>>
>
>>> IDL> a=obj_new('idl_idlbridge')
>
>>
>
>>>
>
>>
>
>>> % Loaded DLM: IDL_IDLBRIDGE.
>
>>
>
>>>
>
>>
>
>>> % Unable to start IDL_IDLBRIDGE slave process.
>
>>
>
>>>
>
>>
>
>>> % Execution halted at: $MAIN$
What happens if you try it with a different "output" path? See this thread:
https://groups.google.com/forum/#!topic/comp.lang.idl-pvwave /INRGnqa9jdw
-Chris
|
|
|
|
|
|
|
|
| Re: Mystical IDL_IDLBridge error [message #89433 is a reply to message #89430] |
Wed, 15 October 2014 09:56 |
chris_torrence@NOSPAM
Messages: 528
Registered: March 2007
|
Senior Member |
|
|
On Wednesday, October 15, 2014 10:26:00 AM UTC-6, Gianguido Cianci wrote:
> Also, in idl 8.1 I get something slightly different:
>
>
>
> IDL> a=obj_new('idl_idlbridge')
>
> % Unable to start IDL_IDLBRIDGE slave process.
>
> % Execution halted at: $MAIN$
>
>
>
> IDL> a=obj_new('idl_idlbridge', output='~/hahha.txt')
>
> % Unable to start IDL_IDLBRIDGE slave process.
>
> % Execution halted at: $MAIN$
>
>
>
> IDL> a=obj_new('idl_idlbridge', output='')
>
> % Dynamically loadable module failed to load: GMEM.
>
> % Execution halted at: $MAIN$
>
> % Dynamically loadable module failed to load: GMEM.
>
> % Execution halted at: $MAIN$
>
>
>
> % Unable to start IDL_IDLBRIDGE slave process.
>
> % Execution halted at: $MAIN$
Do you have some environment variable set that is causing IDL to find the "wrong" IDL bridge executable, or none at all?
If you do "env", do you see anything related to IDL? If so, I would suggest commenting it out in your shell file and see what happens.
-Chris
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
