debugger memviewdialog

Hi,

your patch is basically OK. But it does not work 100%. I
still experienced problems with reloading which seamed to be
related to the startvalue being too big for int. So it is
better to use toUInt(0,0) instead of toInt(0,0).

I attached an updated patch that also fixes the problem that
changes in the memview where not actually done.

If there are no objections I'm going to commit it.

Regards, 
Robert



On Tue, 14 Nov 2006 01:28:06 you wrote:
> The memviewdialog in the debugger doesn't store it's
start address due
> to a wrong conversion.
> So when reload is hit, the memview starts at 0x0
instead of the
> address specified before.
> 
> This was discussed already with Volodya in IRC, but it
maybe got lost.
> I just found it here.





-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu
sparen! 
Ideal für Modem und ISDN: http://www.gmx.n
et/de/go/smartsurfer
_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Friday 17 November 2006 10:45, Robert Gruber wrote:
> Hi,
>
> your patch is basically OK. But it does not work 100%.
I still experienced
> problems with reloading which seamed to be related to
the startvalue being
> too big for int. So it is better to use toUInt(0,0)
instead of toInt(0,0).
>
> I attached an updated patch that also fixes the problem
that changes in the
> memview where not actually done.
>
> If there are no objections I'm going to commit it.

Looks good to me.

Thanks!

- Volodya

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel