From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb@sources.redhat.com
Subject: Re: Query regarding GDB-Mi interface
Date: Wed, 30 Jul 2008 07:07:00 -0000 [thread overview]
Message-ID: <g6p34v$u30$1@ger.gmane.org> (raw)
In-Reply-To: <488FFADA.7040306@mentor.com>
Pankaj Pal wrote:
> We have a debugging front end which uses gdb-6.6 We were using
> annotations till now but
> as annotations have been made obsolete we are shifting to MI
> interpreter. I have a few queries regarding MI.
>
> 1) Why few commands are still un implemented like attach,
Because you are using gdb-6.6. The -target-attach command is implemented
in CVS HEAD.
> info program
> etc. Is there any plan to support them.
I don't have any plan to implement MI version of "info program", in part
because I never heard about this command. Why do you need it?
> 2) Is there any way to stop the MI interpreter like we have with
> annotations (set annotate 0 whenever we wish to do so).
What do you mean "stop"? GDB will always accept MI commands, and output
MI outputs if you've started it in MI mode.
> 3) We need 'info line *addr' command when we are shifting to MI from
> annotations. I have been doing few changes in
> the gdb source code to get this information (source file and line
> number), however annotations have this information.
> I would like to know is there any known issue due to which this
> command has not been implemented.
You can use "info line *addr" just fine, even in MI mode.
> 4) In the gdb manual I can see that 'call' command in gdb is equivalent
> to '-data-evaluate-expression' in MI. But with
> annotations, the 'call' command sequence is as follows ::
> ^z^z starting
> --->> do the call command functionality
> ^z^z stopped
>
> However, with MI, we are not getting the 'running' and 'stopped' tokens.
This is by design, at least for now. Emitting *stopped for calling functions in
inferiour might cause the frontend to reload program state again, which will
cause expressions with functions calls to be reevaluated, which will cause
further *stop, etc. Why is this information necessary for you? Note that I've
posted a patch to optionally enable running/stopped notification for function
calls, I just did not press it further due to lack of support.
- Volodya
next prev parent reply other threads:[~2008-07-30 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 6:53 Pankaj Pal
2008-07-30 7:07 ` Vladimir Prus [this message]
[not found] <488FE9AF.5060008@mentor.com>
[not found] ` <488FF89A.3020609@mentor.com>
2008-08-01 23:34 ` 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='g6p34v$u30$1@ger.gmane.org' \
--to=vladimir@codesourcery.com \
--cc=gdb@sources.redhat.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