Daniel Jacobowitz wrote:
On Fri, Jan 18, 2008 at 10:43:36AM -0800, Pawel Piech wrote:
I think what Marc meant was that after a resume/suspend, even if
-var-update indicates that a given variable hasn't changed the IDE will
need to retrieve it's value because of the ambiguity of the value
formats. However, only variables which are visible on the screen will be
requested by the UI from the service, so if a variable wasn't visible, a
-var-update would never be called for it anyway.
Thanks, I see now. That's still unfortunate, but not as bad as it
sounded. Why does the IDE need to keep track of multiple formats
anyway? Only one is being displayed..
The DSF GDB debugger uses the detail pane in the variables, registers,
and expressions views to display the variable in all available formats
at the same time.
There is a bigger issue here though. The architecture of the debugger
integration in Eclipse separates the UI code (views, actions, etc) and
the non-UI code with an API that abstracts the details of the debugger
back end. However, GDB's design of the variable objects makes some
assumptions about the presentation of the data in the UI, and these
assumptions are making it somewhat difficult to create an efficient
implementation of the non-UI layer of the debugger integration.
Cheers,
Pawel
|
