[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cdt-dev] Re: memory view renderings don't update
|
I need to amend my earlier statement: the memory window doesn't update only when I am using an _expression_ whose value changes each time I break in that function. When I use an absolute address or an _expression_ whose value never changes, it updates fine. So it's as if the memory view doesn't re-evaluate expressions each time the application is suspended.
On Thu, Aug 19, 2010 at 3:58 PM, Tim Black
<timblaktu@xxxxxxxxx> wrote:
When I add a Memory Monitor and a rendering I can correctly see and modify memory. If I resume my application, and break back in the same thread, same function, the Memory Rendering never updates. I can create a new rendering, and the correct memory is shown, but this is extremely cumbersome. This is a problem regardless of whether I use an absolute address or an _expression_ that evaluates to an address.
I was not able to find anything about this issue in the archives or on bugzilla. I am using standard Helios/CDT with GDB 7.1-1 and GDB-DSF debug launchers. This problem plagues me whenever I do any memory viewing. Please let me know if there is a fix, a workaround, or if I should file a bug. Thanks.
