[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-debug-dev] More Debugger Array Viewing Changes...
|
Personally I think that this is a great idea. We ran into a similar
problem in our own serial debug support (whose protocol supports uploading)
and ended up doing a rough bytes / line rate * sanity multiplier
calculation.
Thomas
> -----Original Message-----
> From: Chris Songer [mailto:songer@xxxxxxxxxxxxx]
> Sent: June 25, 2003 6:37 PM
> To: cdt-debug-dev@xxxxxxxxxxx
> Subject: [cdt-debug-dev] More Debugger Array Viewing Changes...
>
>
>
> Hi,
>
> Given GDB performance, we saw CDT start to time out on large array
> requests. The following patch corrects this by scaling the
> time out with
> the number of children being retrieved. I have not looked at
> the head on
> this so your mileage may vary. On 1.0.1 with this and the
> MIParser change
> you can open 16k arrays. I decided the value of testing
> larger sizes was
> not worth it. :)
>
> I should mention that there appears to be a bug / lack of feature in
> VariablesViewContentProvider.getChildren(). It's my personal
> opinion that
> it should use BusyIndicator and a runnable so that an
> hourglass icon pops
> up for these long fetches. There's really no good place to
> put it lower in
> the call chain. It is reasonable to want to look at a 4k
> array. There is a
> noticeable pause for this, it should be covered with an hourglass but
> there's really no way to hook it.
>
> Thanks!
> -Chris
>
