[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [dsdp-dd-dev] Re: [platform-debug-dev] Variable Access Size in a Memory Block
|
Hi John,
> There's the ability to customize the add-monitor action that was
> added in 3.2, but I suspect this requirement is pervasive enough that
> we'd not want to impose that high-cost in order to get that
> capability. Ideally, the platform would expose that parameter if the
> debugger adapter says it supports/needs the capability.
Do you mean that you still think that the platform should have the UI to
allow the user to enter this information?
We need interfaces to ask a debug adapter if it supports this capability
and for passing the access size to the adapter?
I was suggesting that all this work should not be done in the platform.
Instead, a debug adapter, like DSF or CDT, should have interfaces to ask
its engine if this capability is supported. If so, then the adapter will
customize the Add Memory Monitor action to allow the user to enter the
information.
I see this similar to our "Address Space" problem. The platform should
have enough hooks to allow clients to customize the "Add Memory Monitor"
actions and related dialogs. It's up to a debug adapter to implement the
concept of address space. The platform does not understand anything about
address spaces.
Thanks...
Samantha
John Cortell
<john.cortell@fre
escale.com> To
Sent by: "Eclipse Platform Debug component
dsdp-dd-dev-bounc developers list."
es@xxxxxxxxxxx <platform-debug-dev@xxxxxxxxxxx>,
Device Debugging developer
discussions
11/14/2006 12:09 <dsdp-dd-dev@xxxxxxxxxxx>, "Eclipse
PM Platform Debug component developers
list."
<platform-debug-dev@xxxxxxxxxxx>
Please respond to cc
Device Debugging
developer Subject
discussions [dsdp-dd-dev] Re:
<dsdp-dd-dev@ecli [platform-debug-dev] Variable
pse.org> Access Size in a Memory Block
Samantha,
Indeed. The only requirement here is that the user be given a way to
specify the access size. The platform would just pass that parameter
back to the debugger implementation for the add-monitor action.
There's the ability to customize the add-monitor action that was
added in 3.2, but I suspect this requirement is pervasive enough that
we'd not want to impose that high-cost in order to get that
capability. Ideally, the platform would expose that parameter if the
debugger adapter says it supports/needs the capability.
John
At 10:46 AM 11/14/2006, Samantha Chan wrote:
>Hi,
>
>I am looking at the requirement for having variable access size in the
>memory block again:
>https://bugs.eclipse.org/bugs/show_bug.cgi?id=150517
>
>I question if this support should really be added to the debug platform or
>if it should be implemented in the debug adapter itself. (e.g. in CDT,
>DSF, etc.) The access size seems to control the conversation between the
>debug adapter and its debug engine. The engine returns different values
>based on an access size. The UI is not really involved in this
>conversation. The UI's responsibility is to simply renders the content of
>the memory block, regardless of how the memory is fetched from the
backend.
>
>It seems to me that the only UI requirement is to allow the user to
specify
>an access size for a range of memory. This information is then passed
onto
>the debug engine when memory is required from the engine. However, I
would
>consider this UI requirement to be specific to a type of debug adapter and
>should not be put in the platform since not all adapters support variable
>access size in a memory block.
>
>Thoughts on this?
>
>Thanks...
>Samantha
>
>_______________________________________________
>platform-debug-dev mailing list
>platform-debug-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
_______________________________________________
dsdp-dd-dev mailing list
dsdp-dd-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev
