[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cdt-dev] Register context is not stack frame specific
|
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of ??
> Sent: Tuesday, August 24, 2010 3:00 AM
> To: cdt-dev
> Subject: [cdt-dev] Register context is not stack frame specific
>
> Hi guys:
> It's about the Registers View
>
> In CDT 5.0, Registers View will update with the selected stack frame.
> In CDT 6.0, Registers View only updates when switching between threads
>
> I've got some explanations on this in the comments of:
> org.eclipse.cdt.dsf.debug.ui.viewmodel.register.RegisterVMProvider
> Line 168, update()
The comment says:
/*
* Use the execution context in the current selection as the input provider.
* This insures that the REGISTER VIEW will not collapse and expand on stepping or on
* re-selection in the DEBUG VIEW. Currently the register content is not stack frame
* specific. If it were to become so then we would need to modify this policy.
*/
I've been trying things out with GDB and it seems that register content _is_ stack
frame specific. When I change frames in GDB and ask for register content, I get a different
set of content depending on the stack frame that I selected. This makes particular sense
for registers like stack pointer, instruction pointers, but the others too.
CDI does not have this problem.
Seems like a bug to me. And a pretty old one at that.
Can you open a bug?
Thank you
Marc
>
> It's on CDT6.0.2, i check CDT7.0 to find the same answer.
>
> The question is : In CLI usage, we do find different
> registers when switching to another stack frame, why CDT-DSF
> make it remain un-changed?
What do you mean by "CLI usage"?
>
> Thanks a lot!
> Regards
> 邢云
>
>
> ________________________________
>
> 您想拥有和网易免费邮箱一样强大的软件吗? <http://qiye.163.com/?163>
>