Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] MI: Event notification
Date: Fri, 05 Jan 2007 01:18:00 -0000	[thread overview]
Message-ID: <17821.42830.764112.307325@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200701050013.20576.ghost@cs.msu.su>

 > > With a large stack and stepping through the program, I think it is very
 > > noticeable, which is why I frequently try to select a line to run to.
 > 
 > Stepping through the code and typing CLI commands are rather different
 > activities. For entering CLI, full UI state reload is not so problematic.
 > 
 > For stepping:
 > 
 > 	1. I have a proposal for "-var-list --locals" that I think will
 > 	make work with local variables very convenient and fast. I'll post
 > 	that tomorrow.

OK, I'll look at that ( = "-stack-list-locals --create-varobjs"?).

 > 	2. As for -stack-* -- if there any reason why that code cannot detect
 > 	that stack has not changed and quickly return "cached" result.
 > 	That will optimize all existing frontends automatically.

I just wanted to start discussion, not commit the patch.  Let's review it
after you've posted your patch for "-var-list --locals"


-- 
Nick                                           http://www.inet.net.nz/~nickrob


      reply	other threads:[~2007-01-05  1:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-01 23:50 Nick Roberts
2007-01-04 20:26 ` Vladimir Prus
2007-01-04 20:49   ` Nick Roberts
2007-01-04 21:14     ` Vladimir Prus
2007-01-05  1:18       ` 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=17821.42830.764112.307325@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@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