Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-debug-dev] FW: Registers Window not Updating

Title: Message
Yes, now I see. Could you please submit a bug for this?
 
Thanks,
Mikhail
----- Original Message -----
Sent: Friday, June 13, 2003 11:07 AM
Subject: RE: [cdt-debug-dev] FW: Registers Window not Updating

Yes, auto refresh is on and even if I do a manual refresh it doesn't update. With the tracing turned on for the debugger, it shows the -var-evaluate-_expression_ for the registers that have changed but there is no -var-update preceeding it. Consequently, the register value is updated with the cached value and not the actual value.
 
regards
 
Ian
 
-----Original Message-----
From: Mikhail Khodjaiants [mailto:mikhailk@xxxxxxx]
Sent: 13 June 2003 15:48
To: cdt-debug-dev@xxxxxxxxxxx
Subject: Re: [cdt-debug-dev] FW: Registers Window not Updating

Seems to work for me. The 'Auto-Refresh' option of the Registers view is off by default. Did you set it? 
 
Thanks,
Mikhail
----- Original Message -----
Sent: Friday, June 13, 2003 6:33 AM
Subject: [cdt-debug-dev] FW: Registers Window not Updating


Hi

Not really sure if this is a known problem or not  - I tried searching in the bugs for it and couldn't find anything. I am using CDT 1.1.0 and have noticed a problem with the register viewer. Once the registers are displayed in the registers window and the appropriate var objects are created and queried, the register values never change from that point on. The registers whose values have actually changed are highlighted appropriately as these are deduced from a call to "-data-list-changed-registers" but their values do not change. This appears to be due to the fact that a -var-update is not performed on the register variables. As a temporary measure for my own stuff I have overriden the getValueString method of Value in RegisterValue (in org.eclipse.cdt.debug.mi.core.cdi.model) to perfrom the update before the -var-evaluate-_expression_ and this works fine. However, as someone who is very new to Eclipse/CDT and hasn't got his head around the source code yet I am not sure if this is the most appropriate place for this. Anyway, that aside - is this a known problem? Or should I file it as a bug?

Cheers

Ian


Back to the top