This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
GDB MI - differences in -var-create output
- From: "Eran Ifrah" <eran dot ifrah at gmail dot com>
- To: gdb at sourceware dot org
- Date: Sat, 2 Aug 2008 10:32:42 +0300
- Subject: GDB MI - differences in -var-create output
- References: <d557d0790808020028u155860b3k90bd8a793a804452@mail.gmail.com>
Hi List,
This is my first post here, so I hope that this is the correct place
to ask this.
I have developed a GDB plugin for my IDE using the GDB Machine Interface.
I have tested the plugin under Linux and Windows and it seems to
function very good. However, under Mac OSX (10.5.2) (it works well,
but only after I tweaked my GDB MI output parser a bit) the GDB MI
output is a bit difference than the other OSs, for example, running
this command:
-var-create - * <expression>
under Linux & Windows, provides the same output like this:
^done,name="var2",numchild="1",value="{...}",type="orxAABOX"
However, under Mac I get this:
^done,name="var2",numchild="1",type="orxAABOX"
Note the missing 'value={...}' part.
another difference, is in the -data-read-memory command output, On
Windows & Linux, I get this:
...{addr="0x003d3e28",data=["0x00","0xab","0xab","0xab"],ascii="xxxx"}...
But On Mac:
...{addr="0x003d3e28",data={"0x00","0xab","0xab","0xab"},ascii="xxxx"}...
Note the change between square brackets & curly brackets just after
the 'data=' part.
My question is this: is this a bug or by design, cause I hate leaving
parts of my code under #if __MAC__ / #endif
--
Eran Ifrah
eran.ifrah@gmail.com
--
Eran Ifrah
eran.ifrah@gmail.com