Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-debug-dev] Variables and Registers views

FYI to those interested in this view. Further developments are being 
tracked by:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=53640

Darin




"Mikhail Khodjaiants" <mikhailk@xxxxxxx> 
Sent by: platform-debug-dev-admin@xxxxxxxxxxx
03/02/2004 04:50 PM
Please respond to
platform-debug-dev


To
<platform-debug-dev@xxxxxxxxxxx>
cc

Subject
Re: [platform-debug-dev] Variables and Registers views






Darin,

This is the patch for the Registers view and the corresponding changes. It
is created against the HEAD branch, though I tested it for v20040223.

Thank you,
Mikhail

----- Original Message ----- 
From: "Darin Wright" <Darin_Wright@xxxxxxxxxx>
To: <platform-debug-dev@xxxxxxxxxxx>
Sent: Friday, February 27, 2004 5:45 PM
Subject: Re: [platform-debug-dev] Variables and Registers views


> Sure.
>
> Darin
>
>
>
>
> "Mikhail Khodjaiants" <mikhailk@xxxxxxx>
> Sent by: platform-debug-dev-admin@xxxxxxxxxxx
> 02/27/2004 02:34 PM
> Please respond to
> platform-debug-dev
>
>
> To
> <platform-debug-dev@xxxxxxxxxxx>
> cc
>
> Subject
> Re: [platform-debug-dev] Variables and Registers views
>
>
>
>
>
>
> Unfortunately, the "nice" extension of the "VariablesView" class is not
> possible. The "ViewerState" class assumes that all viewer's elements are
> instances of  "IVaraible" which is not true for the registers view.
> However, replacing "ViewerState" by some abstract class with the 
abstract
> "encode" and "decode" methods and providing a protected factory method 
for
> this class will solve the problem.
> Are you interested in these changes?
>
> Thanks,
> Mikhail
> ----- Original Message ----- 
> From: "Darin Wright" <Darin_Wright@xxxxxxxxxx>
> To: <platform-debug-dev@xxxxxxxxxxx>
> Sent: Wednesday, February 25, 2004 3:18 PM
> Subject: Re: [platform-debug-dev] Variables and Registers views
>
>
> > Ideally, you could contribute your registers view to the debug 
platform.
> > Then it could live in an internal package, taking advantage of the 
debug
> > view framework. Currently, we do not have cycles to make the views 
API.
> > Alternatively, you could just subclass our views, knowning that you 
are
> > vulnerable to breakage.
> >
> > Darin
> >
> >
> >
> >
> > "Mikhail Khodjaiants" <mikhailk@xxxxxxx>
> > Sent by: platform-debug-dev-admin@xxxxxxxxxxx
> > 02/25/2004 01:43 PM
> > Please respond to
> > platform-debug-dev
> >
> >
> > To
> > <platform-debug-dev@xxxxxxxxxxx>
> > cc
> >
> > Subject
> > [platform-debug-dev] Variables and Registers views
> >
> >
> >
> >
> >
> >
> > Hi,
> >
> > I am currently working on the new version of the Registers view for 
CDT.
> > Functionally the Registers view is identical to the Variables view. 
The
> > implementation needs some minor changes in the content provider and 
the
> > event handler. The best way to implement this is to do exactly what 
has
> > been done for the Expression view - extend the corresponding classes.
> > Unfortunately, this is not an option, the VariablesView class and all
> > related classes are internal. All I can do now is create copies of the
> > internal classes and follow the changes.
> > Are there any suggestions on how to handle the situations like this
> > differently?
> >
> > Thanks,
> > Mikhail Khodjaiants
> > QNX Software Systems
> >
> > _______________________________________________
> > platform-debug-dev mailing list
> > platform-debug-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/platform-debug-dev
> >
>
> _______________________________________________
> platform-debug-dev mailing list
> platform-debug-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-debug-dev
>
>
> _______________________________________________
> platform-debug-dev mailing list
> platform-debug-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-debug-dev
>
[attachment "regs_patch.txt" deleted by Darin Wright/Ottawa/IBM] 



Back to the top