Hi, I use recently VisualGDB and encountered problem.
To see what is located on the stack very close to the end of memory (0x20020000) I see only zeros. I noticed that the problem is the command “-data-read-memory-bytes <addres> <size>” because the window memory queries, such as those marked in red (picture). Memory ends at 0x20020000. And window memory retrieves data out of range (begin = “0x2001fd88” end = “0x20020010″) and shows only zeros.
In the photo I mentioned in the green that the output of one byte too far returns zero.
<p style=”text-align: right;”><sup>I hope you can understand what I wrote.</sup>
<sup> I tried to find a solution but I could not. (Maybe bad looking)</sup></p>
This topic was modified 8 years, 5 months ago by kurek125.
This topic was modified 8 years, 5 months ago by kurek125.
This topic was modified 8 years, 5 months ago by kurek125.
This topic was modified 8 years, 5 months ago by kurek125.
This topic was modified 8 years, 5 months ago by kurek125.
This topic was modified 8 years, 5 months ago by kurek125.
This is a known issue. Sometimes some gdb stubs report memory contents incorrectly. Please try enabling the “use ‘x’ command to read memory” checkbox in the VisualGDB Project properties (GDB Settings page). This should use a slightly slower but more reliable mechanism.