Re: [cdt-dev] Memory monitors in CDT4.0.2

[subs <dmsubs@xxxxxxxxxxxxx>]

Well, this seems like a *bad idea* to introduce this in a bug fix release.

When my users upgrade they are going to get a new dialog which is completely 
irrelevant, and in fact irrelevant to (I hazard a guess) 99% of CDT users.

So, how do I switch it off?


John Cortell wrote:
> That functionality was introduced in CDT 4.0. It only surfaced for CDI 
> back-ends that claimed to support memory spaces. In 4.0, the gdb CDI 
> client did not claim that support.
>
> However, in 4.0.2, the debugger watchpoint support was improved. That 
> enhancement also included support for memory spaces. And during its 
> development, it was noticed that gdb has built-in support for two memory 
> spaces: code and data, and so at that point, we flipped on the switch in 
> the gdb client--i.e., it now says it supports memory spaces, which is 
> why you're seeing that dialog now.
>
> The work in 4.0 was done under the bugzilla entry:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=114528
>
> John
>
>
> At 12:21 PM 12/4/2007, subs wrote:
> > What happened to memory monitors in CDT4.0.2?
> >
> > In 4.0.2 I now get a new dialog (snapshot attached) asking me to 
> > either "Enter memory space and address" or "Enter Expression".
> >
> > Where did this new functionality come from? Is it the sort of thing 
> > that should have been introduced in a bug-fix release?
> >
> > --
> > Derek
> >
> >
> >
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev

--
Derek