Bug #11741 2007-08-11 10:47
giles
Incorrect memory dump
It happens that the memory dump window displays incorrect data. For example the window may display:
0x7feb4c: 00 00 00 00 08 00 00 00|x: :: 80 00 00 00 08 00 ..........Â.....Æ¿îg
0x7feb5c: 00 00 x: :: f0 0f 00 00|00 10 00 00 x: :: 0a 00 ....ð...........Æ¿îg
if I use the "send user command to debugger" command with
x/32xb 0x7feb4c
I get:
0x7feb4c <VDBasicString<wchar_t>::s_null+8>: 0x00 0x00 0x00 0x00 0x08 0x00 0x00 0x00
0x7feb54 <__gnu_cxx::__mt_alloc<char>::_S_options+4>: 0x80 0x00 0x00 0x00 0x08 0x00 0x00 0x00
0x7feb5c <__gnu_cxx::__mt_alloc<char>::_S_options+12>: 0xf0 0x0f 0x00 0x00 0x00 0x10 0x00 0x00
0x7feb64 <__gnu_cxx::__mt_alloc<char>::_S_options+20>: 0x0a 0x00 0x00 0x00 0x00 0x00 0x00 0x00
I am using Jul 10th 2007 build with mingw
I did not succeed to determine the reproduction conditions
- Category
- Debugger
- Group
- Status
- Open
- Close date
- Assigned to
History
Does this persist with a recent revision?