[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] address spaces
|
Oh, we certainly wouldn't expect something like this to be addressed in
3.0. My understanding is this mailing list is for discussing, among other
things, the future direction of the CDT debug technology. Much of what I'll
be posting to this list regards Freescale requirements and intentions that
we hope to materialize over then next 3 - 12 months.
John
At 09:02 PM 6/9/2005, you wrote:
John,
I don't think we are going to update this for 3.0. Alain has problems with
his e-mail, hopefully he will eventually fix it and we'll get his comments
on ICDILocation.
Mikhail
----- Original Message -----
From: "John Cortell" <r4609c@xxxxxxxxxxxxx>
To: "CDT Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>
Sent: Thursday, June 09, 2005 8:08 PM
Subject: Re: [cdt-debug-dev] address spaces
> [Any comments on this? Would updating CDT (in cases like the one I
> mentioned below and in tweaking IAddress) to support address spaces be
> considered too disruptive?]
>
> Consider ICDILocation - used for breakpoints, among other things. It has
> a getAddress() method that returns a BigInteger. So at least there we
> have one case where it's assumed a memory location can be represented
> with a single integral value. I'm suspecting there are other such cases,
> but I don't know that for sure.
>
> John
>
> At 12:10 PM 6/8/2005, Mikhail Khodjaiants wrote:
>
>
>
> I'm not sure that I'm getting it right, but we use "IAddress" to
> represent
> an address in CDT. We would need to modify the address presentation
> parts,
> but that's a minor thing. Or there is something more generic that I'm
> missing?
>
> ----- Original Message -----
> From: "John Cortell" <r4609c@xxxxxxxxxxxxx>
> To: "CDT Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>; "CDT Debug
> developers list" <cdt-debug-dev@xxxxxxxxxxx>
> Sent: Wednesday, June 08, 2005 2:34 PM
> Subject: Re: [cdt-debug-dev] address spaces
>
> > As per my description, this issue goes beyond the Memory Window.
> Please
> > see
> > my description of the "complete" support level.
> >
> > John
> >
> > At 11:29 AM 6/8/2005, Mikhail Khodjaiants wrote:
> >
> >>It would be better to post this questions to the platform mailing list
>
> >>(platform-debug-dev@xxxxxxxxxxx). The Memory View implementation in
> CDT
> > is
> >>based on the platform framework and UI. The modifications to support
> >>address spaces should be done in the platform.
> >>
> >>----- Original Message -----
> >>From: "John Cortell" <r4609c@xxxxxxxxxxxxx>
> >>To: <cdt-debug-dev@xxxxxxxxxxx>
> >>Sent: Wednesday, June 08, 2005 12:44 PM
> >>Subject: [cdt-debug-dev] address spaces
> >>
> >> > Has there been any meaningful discussions on adding support for
> > address
> >> > spaces in Eclipse/CDT? I understand this was brought up as an item
> > in
> >> > the
> >> > Chicago meeting last month. The way we see it, there are two levels
>
> > of
> >> > support:
> >> >
> >> > - superficial : user can view the contents of memory in different
> >> > address
> >> > spaces in the Memory View.
> >> >
> >> > - complete : variables, expressions and code locations can be in
> >> > different
> >> > address spaces. For this level of support, the debugger
> > infrastructure
> >> > would need to use something other than a primitive integer type to
> >> > represent a memory address. A particular location in memory would
> > have
> >> > to
> >> > be represented by an address + address space identifier.
> >> >
> >> > I understand the need for this sort of thing is particular to the
> >> > embedded
> >> > world. Still, if CDT is to be considered a viable platform for the
> >> > embedded
> >> > market, address spaces will need to be considered.
> >> >
> >> > Thoughts?
> >> >
> >> > John
> >> >
> >> > _______________________________________________
> >> > cdt-debug-dev mailing list
> >> > cdt-debug-dev@xxxxxxxxxxx
> >> >
> >>
> >
<
<<https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev >
> <https://dev.ecli>https://dev.ecli <https://dev.ecli/>
> > pse.org/mailman/listinfo/cdt-debug-dev
> >>
> >>
> >>_______________________________________________
> >>cdt-debug-dev mailing list
> >>cdt-debug-dev@xxxxxxxxxxx
> >><
<<https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev >
<https://dev.ecl>https://dev.ecl
> <https://dev.ecl/>
> > ipse.org/mailman/listinfo/cdt-debug-dev
> >>
> >
> > _______________________________________________
> > cdt-debug-dev mailing list
> > cdt-debug-dev@xxxxxxxxxxx
> >
<<https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
>
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
>
<<https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
>
>
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
<https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
