| Re: Floating divide by 0 [message #45448] |
Fri, 16 September 2005 12:17  |
Michael Wallace
Messages: 409
Registered: December 2003
|
Senior Member |
|
|
>> The problem is with my RETAIN keyword in the IDLgrWindow. I was using
>> RETAIN=0 (the default) and when I have changed to RETAIN=1 (software)
>> is ok.
>>
>> :(
>>
>> More ideas ?
>>
>
> Hello boy, I think you want to say RENDERER instead RETAIN, no?
What kind of system are you using? If you have a problem with the
RENDERER set to 0 (hardware), you might have certain graphics libraries
missing or a driver that doesn't have exactly what IDL needs. Put
another way, it's an issue with libraries and drivers on your system,
not IDL.
I ran into RENDERER problems on another system, a Linux box from a year
or so ago. I had to set LD_ASSUME_KERNEL and couple other crazy
environmental variables and then I was finally able to get things to
work as they should have.
-Mike
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Floating divide by 0 [message #45646 is a reply to message #45451] |
Fri, 16 September 2005 12:30  |
Karl Schultz
Messages: 341
Registered: October 1999
|
Senior Member |
|
|
On Fri, 16 Sep 2005 20:56:36 +0200, Antonio Santiago wrote:
> Antonio Santiago wrote:
>> Oh, my God.
>>
>> The problem is with my RETAIN keyword in the IDLgrWindow. I was using
>> RETAIN=0 (the default) and when I have changed to RETAIN=1 (software) is
>> ok.
>>
>> :(
>>
>> More ideas ?
>>
>
> Hello boy, I think you want to say RENDERER instead RETAIN, no?
When a problem like this goes away by switching from hardware to software
rendering, it is very likely caused by a display driver problem, most
likely in the OpenGL drivers.
You might want to check for a driver update from your card manufacturer.
The exceptions are getting generated in the OpenGL driver code called by
IDL and the IDL exception handlers are noticing the exceptions and
reporting them.
Karl
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
