Bug 167970 - Memory Window is not completely updated when addressable size > 1
Summary: Memory Window is not completely updated when addressable size > 1
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-memory (show other bugs)
Version: 6.0   Edit
Hardware: PC Windows XP
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
: 161859 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-12-13 17:05 EST by Alain Lee CLA
Modified: 2020-09-04 15:26 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alain Lee CLA 2006-12-13 17:05:54 EST
I was testing the Traditional Memory Window with a 32-bit simulator and found that my memory window is half blank. Further diagnosis confirmed that MemoryRenderingTraditional::getBytes() failed to access a particular byte. 

Here is some info that may help you debug:
Addressable size = 4
fCache.start =1000
fCache.end =1120 
fCache.bytes[30]

When exception occurred, getBytes(1027, 4) was executing  fCache.bytes[offset + i] where offset=27 and i=3. The code was actually trying to get the memory for address 1027. It seems to me that populateCache() did not read all the bytes that represent the addresses in the range between fCache.start and fCache.end.
Comment 1 James Blackburn CLA 2011-03-17 14:02:11 EDT
Traditional Memory Rendering now lives in CDT -> moving bugs
Comment 2 Randy Rohrbach CLA 2012-05-23 10:41:34 EDT
*** Bug 161859 has been marked as a duplicate of this bug. ***