Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: Formatting of function pointer value
Date: Mon, 11 Jul 2005 13:08:00 -0000	[thread overview]
Message-ID: <20050711130742.GB25755@nevyn.them.org> (raw)
In-Reply-To: <dat7p6$4s2$1@sea.gmane.org>

On Mon, Jul 11, 2005 at 11:40:21AM +0400, Vladimir Prus wrote:
> Vladimir Prus wrote:
> 
> > Ok, the the only advantage of MI is stable output format. Can you tell me
> > how it's achieved? For example, looking at the code that prints function
> > values (what worries me in the first place):
> > 
> >    fprintf_filtered (stream, "{");
> >    type_print (type, "", stream, -1);
> >    fprintf_filtered (stream, "} ");
> > 
> > As I right in assuming that exactly the same output will be produced for
> > MI mode and for CLI mode? If so, then how MI can be more stable than CLI,
> > if the output is the same?
> 
> To clarify more, here's what I get with MI:
> 
>    -data-evaluate-expression *p3
>    ^done,value="{int (int)} 0xb7ee6e9c <__DTOR_END__+4>"
>    (gdb)
>    -var-create VP3 0 *p3
>    ^done,name="VP3",numchild="0",type="int (int)"
>    (gdb)
>    -var-evaluate-expression VP3
>    ^done,value="{int (int)} 0xb7ee6e9c <__DTOR_END__+4>"
> 
> The type enclosed in {} is still there.

The intention is that this is a user-readable value, to be displayed. 
There's limited facility for computing values with machine-readable
results, probably because there has been limited need for it to date.
You can get some information more precisely - for instance the type.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-07-11 13:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08  8:02 Vladimir Prus
2005-07-08  8:51 ` Vladimir Prus
2005-07-08 13:59   ` Daniel Jacobowitz
2005-07-11  5:40     ` Vladimir Prus
2005-07-11  7:11       ` Vladimir Prus
2005-07-11  8:35       ` Andreas Schwab
2005-07-11 13:03         ` Daniel Jacobowitz
2005-07-08 13:58 ` Daniel Jacobowitz
2005-07-11  5:38   ` Vladimir Prus
2005-07-11  7:06     ` Nick Roberts
2005-07-11  7:21       ` Vladimir Prus
2005-07-11  7:42         ` Vladimir Prus
2005-07-11 13:08           ` Daniel Jacobowitz [this message]
2005-07-11 13:21             ` Vladimir Prus
2005-07-11 13:27               ` Daniel Jacobowitz
2005-07-14  8:10                 ` Vladimir Prus
2005-07-11  8:08         ` Nick Roberts
2005-07-11  9:05           ` Vladimir Prus
2005-07-11  9:53             ` 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=20050711130742.GB25755@nevyn.them.org \
    --to=drow@false.org \
    --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