| _EXTRA inheritance crashing IDL [message #34870] |
Tue, 29 April 2003 12:50  |
mal11
Messages: 1
Registered: April 2003
|
Junior Member |
|
|
In IDL 5.6, it appears that the fatal _REF_EXTRA bug was fixed, but I
am wondering if I have found another bug. Try these 2 simple
procedures:
PRO test1, _REF_EXTRA=ex
test2, _EXTRA=ex
;test2, _EXTRA=['BLAH1','BLAH2']
END
PRO test2, BLAH1 = blah1, BLAH2 = blah2
PRINT, "test2 called"
IF KEYWORD_SET(blah1) THEN PRINT, "Blah1 passed!"
IF KEYWORD_SET(blah2) THEN PRINT, "Blah2 passed!"
END
Notice the first way of calling test2 in test1. This has all the
expected behavior. The second manner that is commented out should work
the same.
But try passing just one keyword.
test1, BLAH2=2.0
For me with IDL 5.6 under WinXP Pro, this crashes IDLDE with an
invalid memory read. If someone else can confirm that this is a bug,
I will report it...
Regards
Matthew Lewis
UT Southwestern Medical Center at Dallas
In article <a950i2$6j6$1@newsreader.mailgate.org>, "Mark Hadfield"
<m.hadfield@niwa.co.nz> wrote:
>
> Yes it's a bug. Report it to IDL.
>
I did, and found that it is a known issue, to be fixed in version 5.6.
David asked for RSI's response to be posted, so here goes:
------------------
RE: Incident #: 120580 Tech Support Submission
I believe in your case, however, that you are actually
experiencing the symptoms of a known bug that appeared first in IDL
5.5, and
has already been identified and recoded for subsequent release in IDL
5.6.
Here is the bug report:
"Title: "Passing _REF_EXTRA keyword name without specifying keyword
crashes
IDL"
Description:
Compile the following procedures in IDL:
pro test2, junk=junk
print, 'hi'
end
pro test, _REF_EXTRA=_extra
test2, _Extra='junk'
end
Calling "test" without passing the JUNK keyword causes a SegFault on
Solaris
and dereference error (at 0xfffffffc) on Windows, and crashes IDL.
Resolution:
This is an internal logic error, in which IDL was looking for
_REF_EXTRA
variables to pass on even though the current frame has no such
variables."
James Jay Jones
Technical Support Engineer
RSI Incorporated
Tel: +1 (303) 413-3920
Email: support@rsinc.com
-------------------
|
|
|
|
| Re: _EXTRA inheritance crashing IDL [message #34966 is a reply to message #34870] |
Tue, 29 April 2003 15:05  |
Mark Hadfield
Messages: 783
Registered: May 1995
|
Senior Member |
|
|
"M A lewis" <mal11@po.cwru.edu> wrote in message
news:c8765746.0304291150.534f349b@posting.google.com...
> In IDL 5.6, it appears that the fatal _REF_EXTRA bug was fixed, but I
> am wondering if I have found another bug. Try these 2 simple
> procedures:
> PRO test1, _REF_EXTRA=ex
> test2, _EXTRA=ex
> ;test2, _EXTRA=['BLAH1','BLAH2']
> END
>
> PRO test2, BLAH1 = blah1, BLAH2 = blah2
> PRINT, "test2 called"
> IF KEYWORD_SET(blah1) THEN PRINT, "Blah1 passed!"
> IF KEYWORD_SET(blah2) THEN PRINT, "Blah2 passed!"
> END
>
> Notice the first way of calling test2 in test1. This has all the
> expected behavior. The second manner that is commented out should work
> the same. But try passing just one keyword.
> test1, BLAH2=2.0
> For me with IDL 5.6 under WinXP Pro, this crashes IDLDE with an
> invalid memory read. If someone else can confirm that this is a bug,
> I will report it...
I get it too (IDL 5.6 on Win 2000). It's not 100% consistent. In playing
around with your example I managed to crash IDLDE several times in the way
you describe, but in my current session everything seems to be working OK.
(I think it's something to do with the order in which I tried things out.)
And on one occasion I got an internal memory error rather than a crash (I
didn't note it down at the time, but it was something about an invalid
IDL_kwvariable)
By the way, why are you using the _EXTRA=['BLAH1','BLAH2'] syntax? I haven't
found it very useful.
--
Mark Hadfield "Ka puwaha te tai nei, Hoea tatou"
m.hadfield@niwa.co.nz
National Institute for Water and Atmospheric Research (NIWA)
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
