Community
Participate
Working Groups
Build Identifier: 20110218-0911 MemoryRenderingElements created by the MemorySegmentLabelAdapter class will somtimes be giving incorrect cell address values. The issue occurs when the addressable size of memory is greater than one byte, and when the table in a memory view contains more than one column. The exact problem can be traced to the following method: private MemoryRenderingElement getMemoryRenderingElement(MemorySegment line, BigInteger lineAddress, int offset, AbstractBaseTableRendering rendering) { BigInteger cellAddress = lineAddress.add(BigInteger.valueOf(offset)); MemoryByte[] bytes = line.getBytes(offset, rendering.getBytesPerColumn()); // make a copy to ensure that the memory bytes are not overwritten // by clients MemoryByte[] copy = new MemoryByte[bytes.length]; System.arraycopy(bytes, 0, copy, 0, bytes.length); MemoryRenderingElement renderingElement = new MemoryRenderingElement( rendering, cellAddress, copy); return renderingElement; } the problem actually occurs in the first line of the method: BigInteger cellAddress = lineAddress.add(BigInteger.valueOf(offset)); To fix this issue, the offset needs to be divided by the addressable size: BigInteger cellAddress = lineAddress.add(BigInteger.valueOf(offset/redering.getAddressableSize())); Reproducible: Always Steps to Reproduce: 1.Create a memory block that has an addressable size of greater than one byte 2.open a memory view and format the view to have multiple columns per row 3.add a color adaptor to the memory block and check the address values of MemoryRenderingElements that are passed to either getForeground() or getBackground().
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Anyone interested in working on this?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
*** This bug has been marked as a duplicate of bug 575413 ***
Reopening. This issue was not addressed by the fix for bug 575413.