From: "Eran Ifrah" <eran.ifrah@gmail.com>
To: gdb@sourceware.org
Subject: GDB MI - differences in -var-create output
Date: Sat, 02 Aug 2008 07:33:00 -0000 [thread overview]
Message-ID: <d557d0790808020032u17cda74k7b25c7dc383bae0a@mail.gmail.com> (raw)
In-Reply-To: <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
next parent reply other threads:[~2008-08-02 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d557d0790808020028u155860b3k90bd8a793a804452@mail.gmail.com>
2008-08-02 7:33 ` Eran Ifrah [this message]
2008-08-02 7:57 ` Nick Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d557d0790808020032u17cda74k7b25c7dc383bae0a@mail.gmail.com \
--to=eran.ifrah@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox