| examine vi gdb/MI fails [message #209346] |
Thu, 07 February 2008 07:48 |
Eclipse User |
|
|
|
Originally posted by: ullrich.martini.gi-de.com
Hello,
I am experiencing the following problem when using eclipse and gdb via
JTAG to a remote target:
I can connect, start, stop, step, set breakpoints, inspect variables.
However, I cannot examine the contents of a pointer via the variables or
memory window.
In the gdb console it looks like the following output generated by Eclipse
when I tried to open the memory dump window and look at the memory area
starting at address 0x67000:
604-data-read-memory 421888 x 1 1 100
604^done,addr="0x00421888",nr-bytes="100",total-bytes="100 ",next-row="0x004218ec",prev-row="0x00421824",next-page= "0x004218ec",prev-page="0x00421824",memory=[{addr="0x00421888 ",data=["0xff"
<...more 0xff following >]}]
(gdb)
605-data-read-memory 421568 x 1 1 736
605^done,addr="0x00421568",nr-bytes="736",total-bytes="736 ",next-row="0x00421848",prev-row="0x00421288",next-page= "0x00421848",prev-page="0x00421288",memory=[{addr="0x00421568 ",data=["0xff"
<...more 0xff following >]}]
421888=0x67000. It seems that eclipse or cdt converts the adress into
decimal format, but gdb interprets it as hexadecimal even although the
'0x' prefix is not there.
If I look at the adress as a sting (e.g. via the variable windows, the
contents will be displayed correctly, but in ASCII and not hex)
Thus, one could argue that this is a gdb issue, and yes, I will post the
same story on a gdb list.
However, my questions to the eclipse community would be:
1) Is my interpretation correct?
2) Can I configure eclipse such that the output would be in hexadecimal
format so that gdb can't misread it so that it would emit:
604-data-read-memory 0x67000 x 1 1 100
I am using Eclipse
Version: 3.3.1.1
Build id: M20071023-1652
and the Zylin embedded cdt plugin
4.1.14
and gdb
6.5.50.20060612-cvs
from yagarto
on windows -x
thanks in advance,
Ullrich
|
|
|
Powered by
FUDForum. Page generated in 0.04650 seconds
Home