From: Pedro Alves <palves@redhat.com>
To: webquinty quinty <webquinty@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB and GDB/MI different reponses....
Date: Thu, 04 Apr 2013 09:35:00 -0000 [thread overview]
Message-ID: <515D495A.2040207@redhat.com> (raw)
In-Reply-To: <CAFTqdrPKfdUH1qn0O5fB499uEPjs-_eecPd0GZFrc2M0S-f0GA@mail.gmail.com>
On 03/21/2013 04:30 PM, webquinty quinty wrote:
> Hello,
>
> As you known, with GDB it is possible to obtain debug information from
> executable.
>
> For example in GDB you can ask about type of var:
>
> -> whatis var
> <- type = unsigned char
>
> I just finished a frontend to extract debug information from a process
> using GDB/MI but the response is different than when I use GDB.
>
> For example, a struct called 'par' GDB return me type=param_typ but GDB/MI
> return me anonimous struct.
>
> Why?
This is the sort of question that is simply impossible to answer definitely
without having the binary in question, or even knowing exactly what you have
attempted. Please don't make us guess; be proactive. But in principle there
should be no difference.
I'd guess either you've used different GDBs for the CLI vs MI tests, or,
you have more than one 'par' in your program, and depending on current context
(what the current function/frame GDB has selected for inspecting) and perhaps
phase of the moon, you'll get one answer or the other.
--
Pedro Alves
next prev parent reply other threads:[~2013-04-04 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFTqdrNmXCMTaJ8vHngQ3n9WMQy98TUoT7JO4MEU0j=JmKJ+yg@mail.gmail.com>
2013-03-21 16:30 ` webquinty quinty
2013-04-04 9:35 ` Pedro Alves [this message]
[not found] ` <515D425E.90001@larraioz.com>
2013-04-04 10:15 ` Pedro Alves
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=515D495A.2040207@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=webquinty@gmail.com \
/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