Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: gdb-patches@sources.redhat.com, bob_rossi@cox.net
Subject: Re: [rfc] Annotation level THREE
Date: Mon, 17 Mar 2003 20:38:00 -0000	[thread overview]
Message-ID: <3E763228.9060104@redhat.com> (raw)
In-Reply-To: <15990.10811.61395.996906@nick.uklinux.net>


>  > 
>  > Why do you need display-{begin,end}?  -display-insert has been made 
>  > redundant by the varobj stuff - it lets the GUI efficiently track its 
>  > display values outside of the CLI.  
> 
> Variable objects don't auto-display. You seem to have to type
> -var-evaluate-expression each time the program stops. 

Why do you need auto-display?  What are you using it for?

Remember, every time the target changes (e.g., from a user modifying a 
variable or register), the display needs to be updated.  This is because 
that variable/register has the potential to modify every single value 
being displayed.  Further, unless your using some sort of changes-only 
mechanism, such as provided by the varobj, the display windows are just 
not going to scale.

>  >  The testsuite is a good source of 
>  > varobj examples (unfortunatly lacking from the doco):
>  > http://sources.redhat.com/gdb/current/onlinedocs/gdb_25.html#SEC565
> 
> The lack of documentation for (and apparent completeness of) GDB/MI is part of
> the problem.

Um, the varobj is documented.  It just lacks a vew concrete examples. 
Those can be found by examining the testsuite.  Both Apple and Eclipse 
are using this part of the MI.

>  > The above list also contains thing like field-{begin,end}, 
>  > array-section-{begin,end} et.al.  Why are they needed.
> 
> I use them to parse the output. They could probably go, if necessary, but
> others that you plan to take out *are* needed.

Can you please be more specific?

Andrew



  reply	other threads:[~2003-03-17 20:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11 23:37 Andrew Cagney
2003-03-12 18:54 ` David Carlton
2003-03-12 19:04   ` Andrew Cagney
2003-03-14  0:08 ` Nick Roberts
2003-03-17  0:23   ` Andrew Cagney
2003-03-17 20:07     ` Nick Roberts
2003-03-17 20:38       ` Andrew Cagney [this message]
2003-03-18 10:31         ` Nick Roberts
2003-03-18 15:29           ` Andrew Cagney
2003-03-18 16:00           ` Andrew Cagney
2003-03-18 20:17             ` Bob Rossi
2003-03-12  6:09 Michael Elizabeth Chastain
2003-03-12 14:50 ` Andrew Cagney
2003-03-12 14:56   ` Daniel Jacobowitz
2003-03-12 17:04   ` David Carlton

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=3E763228.9060104@redhat.com \
    --to=ac131313@redhat.com \
    --cc=bob_rossi@cox.net \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nick@nick.uklinux.net \
    /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