At 12:54 AM 1/19/00 -0100, Paul Kinnucan wrote:
>At 10:03 PM 1/18/00 -0100, Paul Kinnucan wrote:
>>At 07:21 PM 1/18/00 -0500, Martin Dickau wrote:
>>>I get the following error in JDE-2.1.6beta16 (both the first version and
the
>>>second one) when I try to display an object:
>>>
>>>Unbound slot: "#<class jde-dbs-java-array>", "#<jde-dbs-java-array array
>>>1544>", length, oref
>>>
>>>Seems to happen on any object. The number seems somewhat related to the ID
>>>of the object I'm displaying in that it is always bigger (the above example
>>>is displaying object 1538; I tried 1557 and got the same string with
1558 as
>>>the number)
>>>
>>
>>
>>This may be a regression bug. I revamped the array display code to support
>the
>>new automatic locals display. I didn't test the display array and object
>>commands
>>to see how they were affected by the changes, in part, because I intend for
>>these
>>commands to go away in the next release. In the next release, when you
>display
>>a variable or evaluate an expression, JDEbug will automatically display
>>object and
>>array values.
>>
>
>Hi Martin,
>
>The Display->Array command works fine on my Windows 95/JDK 1.3beta/JDE
>2.1.6beta16 setup. Please rerun the command and then use JDE->Help Submit
>Bug Report to generate a dump of your environment and send it to me.
>
Hi Martin,
More on arrays. If you try to display a very large array, it's possible
that the JDE may get impatient waiting for results and give up waiting.
I do not currently check for this condition and hence the error you
see may be secondary. I will look into this further and provide
more robust handling for displaying large arrays. In the meantime, you
can try setting the debug command time out variable to some large number.
- Paul
