[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-dev] memory monitor on pointer variable
|
Hi,
>>
Currently, when you add a memory monitor as an _expression_,
in the memory view,
>>DSF stores the value of that _expression_ and the label (the
_expression_ itself). That memory
>> address is fixed and is not updated. Because of this problem is, even if the variable is renamed and again relaunched what it does is, it tries to create memory monitor with same _expression_ and address (which was saved earlier by DSF), even if the variable does not exist.
>>
I
think there is room for improvement there, at least for the user-friendliness
part.
Will it be a good idea to have a toolbar action or pop up menu say "Refresh Memory Block" which will re-evaluate the _expression_ and if there is any change in the address then we can update the user interface.
If so I can try to contribute a patch for it.
Thanks
Harish Dewan
Tensilica India
On Mon, Jan 23, 2012 at 9:32 PM, Marc Khouzam
<marc.khouzam@xxxxxxxxxxxx> wrote:
Hi,
Currently, when you add a memory monitor as an _expression_,
in the memory view,
DSF stores the value of that _expression_ and the label (the
_expression_ itself). That memory
address is fixed and is not updated. In fact, if you
re-launch, your 'my_ptr' monitor
will still show the memory address that you were showing in
the previous launch,
even if the _expression_ 'my_ptr' is currently completely
different.
I
don't like this myself, but I wonder if there isn't a reason behind
it.
For
example, maybe the user expects a memory monitor to be fixed so
as
to
look at the same memory all the time. (If that is the case, maybe
we
should
show the absolute addres instead of the _expression_ as the
monitor).
I'm
curious to know if more experienced people have an
explanation.
Could
be a behavior based on the platform even...
I
think there is room for improvement there, at least for the user-friendliness
part.
Marc
Hi All,
I have a question regarding memory view.
Put memory
monitor on pointer variable , it does not updates its memory address when we
step,
consider a simple program,
int main()
{
int
i=100,*my_ptr,x=5,a=3,b=4,c=5,d=6;
my_ptr=&i;
my_ptr=&x;
my_ptr=&a;
return
0;
}
if I add memory monitor on 'my_ptr' , say address
while I planted memory monitor my_ptr was at address 0xe8e8e8e8
now when I
step, address of 'my_ptr' changes but in memory view it does not
updates.
But if I add another memory monitor at 'my_ptr' it will show
correct address.
so is this the desired behavior or is it a
bug.
Thanks
Harish Dewan
Tensilica
India
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev