[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-debug-dev] Memory View
|
To support addressable unit size larger than 8 bits, you need to implement
IMemoryBlockExtension. In your implementation, you need to return the
correct addressable size in this API:
public int getAddressableSize() throws DebugException;
Please note that #getAddressableSize returns the minimum number of "bytes"
that can be retrieved as a single unit.
Thanks...
Samantha
Khaled ABDA
<khaled.abda@st.c
om> To
Sent by: <platform-debug-dev@xxxxxxxxxxx>,
platform-debug-de <cdt-debug-dev@xxxxxxxxxxx>
v-bounces@eclipse cc
.org
Subject
[platform-debug-dev] Memory View
30/10/2007 09:04
AM
Please respond to
"Eclipse Platform
Debug component
developers list."
<platform-debug-d
ev@xxxxxxxxxxx>
Hello
I come to read on the "Eclipse Corner Articles"
That the "IMemoryBlock is not capable to represent systems that has not
byte-size addressable units"
So, PLZ how to proceed to use the Eclipse Memory View to get and Set Memory
for Systems whose minimum addressable unit size is larger than 8-bit
example (10,12 or 14 bits)...
Is there any way to do that or not ...
I have re-implemented some classes such IMemoryBlock ... But I found no
issue
Since the Debugger itself manages only bytes.
Regards
Khaled ABDA
-----Original Message-----
From: abdak [mailto:khaled.abda@xxxxxx]
Sent: Tuesday, October 30, 2007 1:49 PM
To: 'platform-debug-dev@xxxxxxxxxxx'; 'cdt-debug-dev@xxxxxxxxxxx'
Subject: MemoryBlock retrieval : PLZ Urgent
Hello
I want to manage the memory data of my target
I want to reuse the standard Memory view of eclipe
The Problem is that :
1/ My target has a Pixel Mode
So that I don't manage(set or get) blocks of Bytes but
Blocks of Pixels (10 or 12 or 14 bits)
2/ The eclipse Debug plugin and CDT manages blocks of "bytes".
I have extended and re-implemented many class and interface
In order to getPixels and Set them instead of Bytes.
(classes such CMemoryBlockExtension, IMemoryBlock,
IMemoryBlockExtension...)
Every thing seems to go well
But the last problem in my CMemoryBlockExtension(ForPixel) urged me to
implement
My own CMemoryBlockRetrievalExtension
In this later
I faced the Big problem which is that the debugPlugin activator gets
MemoryBlocks which are (IMemoryBlock[])
DebugPlugin.getDefault().getMemoryBlockManager().getMemoryBlocks()
And gives no way to get my own (IMemoryBlockForPixel[]) which manages
pixels and not bytes
I want to know if the debugPlugin returns only block of Bytes or it doesn't
care of that
So I could cast the block like this
public String getMemento() throws CoreException {
IMemoryBlockForPixel[] blocks =(IMemoryBlockForPixel[])
DebugPlugin.getDefault().getMemoryBlockManager().getMemoryBlocks(
getDebugTarget() );
..........
}
NB :[CMemoryBlockExtensionForPixel will be the class "instanceOf" of my
"renderingBingings"
Corresponding to my new "renderingType"]
I see that the question is long and compilcated to explain
But your answer will be of great help for me
Thanks in advance.
Khaled ABDA
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev