[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-debug-dev] Call stack update
|
Todd,
This is a known problem (see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=48613). The current
implementation needs some serious changes to fix it.
Can you submit a bug with your suggestions? I don't know all possible cases
when the stack update is necessary.
Thanks,
Mikhail Khodjaiants
----- Original Message -----
From: "Power, Todd" <tpower@xxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>
Sent: Tuesday, November 29, 2005 11:52 AM
Subject: [cdt-debug-dev] Call stack update
Hi,
We have a number of cases in which a target's call stack can change
without the target having been resumed and then suspended. These
include PC writes, certain memory writes, symbol changes, and under some
circumstances stepping. However, the only way to change the call stack
appears to be to fire an ICDIResumedEvent, which invalidates the call
stack, and then fire an ICDISuspendedEvent event, which causes the stack
to be rebuilt. Since the target is not being resumed and suspended
though, I'd rather not fire these events just to update the call stack.
Does anyone have any suggestions?
Thanks,
Todd Power
Texas instruments