Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tcf-dev] Support for multiple address spaces?

Hello Eugene,

I think that works very well for address spaces that fully contain the
execution contexts (software threads or hardware cores), such as software
processes or virtual memory of "normal" processors.

I don't think it works well when the relationships between threads or cores
and memory spaces are something other than that.

For instance, on a simple Harvard architecture microcontroller core, each
stack frame will typically contain pointers to data memory as well as
pointers to constant data in program memory. The user may want to inspect
the targets of both in the memory view. What would a single hierarchy in the
Debug view look like to support that?

If the agent adds top level contexts for data and program memory, the user
would lose all context when he / she  selects one of them for the benefit of
the Memory view, since the selection in the Debug view drives all views. 

In our case, the situation is more complex than that. Since the debug engine
has visibility into all memory, even in peripheral devices, even a small
system will easily have 40 or more accessible memory spaces. The debug view
would become very cluttered with things that are only relevant to the Memory
view.

Thoughts?

Regards

Mattias Bertilsson
   
-----Original Message-----
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On
Behalf Of Eugene Tarassov
Sent: den 1 juli 2020 20:51
To: TCF Development
Subject: Re: [tcf-dev] Support for multiple address spaces?

Hi Mattias,

In TCF, multiple address spaces represented by items (debug contexts) in the
Debug view.
It is up to debug target (TCF agent) to report debug contexts hierarchy,
which properly represents available address spaces.
This approach works fine for me. I don't see a need to implement
IMemorySpaceAwareMemoryBlockRetrieval.

Regards,
Eugene

-----Original Message-----
From: tcf-dev-bounces@xxxxxxxxxxx <tcf-dev-bounces@xxxxxxxxxxx> On Behalf Of
Mattias Bertilsson
Sent: Wednesday, July 1, 2020 10:29 AM
To: tcf-dev@xxxxxxxxxxx
Subject: [tcf-dev] Support for multiple address spaces?

CAUTION: This message has originated from an External Source. Please use
proper judgment and caution when opening attachments, clicking links, or
responding to this email.


Hello all,

Investigating support for multiple address spaces in an Eclipse and TCF
based debug solution we have, I came across this old discussion (
https://www.eclipse.org/lists/tcf-dev/msg00846.html ).

It looks to me like the Memory view, combined with CDT, already has support
for multiple address spaces, but you have to provide the right adapters for
it to kick in (and do some additional work) and I think the TCF plugins
currently do not do that?

Details from when this feature was added are available here (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=114528#c25 ). This is old, so
many things are out of date, but it looks to me like the DSF/GDB plugins do
make use of it (GdbMemoryBlockRetrieval implementing
IMemorySpaceAwareMemoryBlockRetrieval, etc).

Has anyone looked into this lately?

Regards

Mattias Bertilsson
_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tcf-dev
_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tcf-dev



Back to the top