-var-update @

[Nick Roberts]

 > DSF only updates varObj that are visible on screen.  So currently, it always
 > uses -var-update with a single varObj name (never use *).

Which must mean that there is a round trip to the target for each variable
object that needs to be updated.

This is sounds similar to the previous discussion about using
"-var-list-children --all-values".  There Daniel stated that "for a lot of
embedded targets [...] reading memory becomes the dominant time delay".

Can someone give some typical numbers for "round trip time" vs "reading memory"
time.  In my naive understanding of embedded targets, I would have thought the
"round trip time" might be large due to a slow serial link, while "reading
memory" wouldn't change much as all RAM is pretty much the same.  Or is the
latter slow because of the time taken to transfer any unneeded extra data back
to the host?

-- 
Nick                                           http://www.inet.net.nz/~nickrob