Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: Formatting of function pointer value
Date: Mon, 11 Jul 2005 09:53:00 -0000	[thread overview]
Message-ID: <17106.16846.134992.221438@farnswood.snap.net.nz> (raw)
In-Reply-To: <data7r$atj$1@sea.gmane.org>

 > >  > Ok, the the only advantage of MI is stable output format.
 > > 
 > > I've not said that.  It also uses variable objects, it aims to be
 > > asynchronous...
 > 
 > Could you give more details? Basically, Daniel suggested that I use MI
 > instead of CLI.

I think thats sound advice.  If you use CLI for KDevelop (?) and then GDB
developers change the CLI output, it will break things for you and you'll have
wasted a lot of effort.

 > I've asked about the reasons why I should, and if possible, I'd like to see
 > all reasons, with a easy to understand descriptions.

I don't think you'll get that.  GDB is a voluntary project.  You just have
to work with what's available (or pay someone).

 > For example, the term "variable objects" says nothing to me, and it's
 > description:
 > 
 >    For the implementation of a variable debugger window (locals, watched
 >    expressions, etc.), we are proposing the adaptation of the existing code
 >    used by `Insight'.
 >
 > does not sched might light either.

I've learnt what I know about variable objects from using Insight, reading
the manual and looking at the source code.  I still don't understand the
asynchronous operation which only works under limited conditions.

 ...
 > >  > 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, "} ");
 > > 
 > > I don't understand the point of the example.
 > 
 > The point of the example is that this code seem to be executed both in MI
 > and CLI modes. So, if '{' is changed to '(', it will equally affect MI and
 > CLI, which makes me wonder why MI is more stable that CLI.

If you are going to generalise the whole of MI and CLI from this one very
small example, then I can see that it would make you wonder why MI is more
stable that CLI

 > As you can see from my other post, the formatting of value is indeed the
 > same for MI and CLI.

Yes, but you can easily parse the MI output and replace '{' with whatever
you want.

Nick


      reply	other threads:[~2005-07-11  9:53 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
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 [this message]

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=17106.16846.134992.221438@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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