Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: webquinty quinty <webquinty@gmail.com>
To: gdb@sourceware.org
Subject: Re: GDB and GDB/MI different reponses....
Date: Thu, 21 Mar 2013 16:30:00 -0000	[thread overview]
Message-ID: <CAFTqdrPKfdUH1qn0O5fB499uEPjs-_eecPd0GZFrc2M0S-f0GA@mail.gmail.com> (raw)
In-Reply-To: <CAFTqdrNmXCMTaJ8vHngQ3n9WMQy98TUoT7JO4MEU0j=JmKJ+yg@mail.gmail.com>

 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?

 Best regards


       reply	other threads:[~2013-03-21 16:30 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 [this message]
2013-04-04  9:35   ` Pedro Alves
     [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=CAFTqdrPKfdUH1qn0O5fB499uEPjs-_eecPd0GZFrc2M0S-f0GA@mail.gmail.com \
    --to=webquinty@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