unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Miles Bader <miles@gnu.org>
Cc: David Hansen <david.hansen@gmx.net>, emacs-devel@gnu.org
Subject: Re: gdb-ui, dedicated windows
Date: Wed, 9 Jul 2008 22:47:26 +1200	[thread overview]
Message-ID: <18548.38718.630083.307385@kahikatea.snap.net.nz> (raw)
In-Reply-To: <871w24ndmd.fsf@catnip.gol.com>

 > gud/gdb-ui shouldn't be storing window references like that and assuming
 > the associated buffer hasn't been changed by the user, because that's an
 > assumption that doesn't hold in emacs.
 > 
 > Perhaps that code is left over from the "old" gdb-ui which used
 > dedicated windows?
 > 
 > A possible fix would be to store the buffer gdb puts in that window,
 > and when deciding whether to re-use that window or, also verify that the
 > same buffer is there (and don't re-use the window if not).

gdb-ui _does_ store the (source) buffer it puts in the window.  That's why when
you replace it with the GUD buffer using switch-to-buffer (not part of gdb-ui)
it gets confused.

It could verify that the same buffer is there but the contents of the source
window change every time the program being debugged stops in a frame that is in
a different file and gdb-ui must allow for this.  If the current window shows
the previous frame and execution is continued (from the tool bar, say) so that
it stops in another frame in a different file, then it's probably appropriate
to replace the entire window with one displaying the new file.

I'm not saying it that can't be done but it's probably more productive to
discuss these ideas with actual code.


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




  reply	other threads:[~2008-07-09 10:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-05  7:58 gdb-ui, dedicated windows David Hansen
2008-07-05 10:02 ` Nick Roberts
2008-07-05 10:52   ` David Hansen
2008-07-07  4:38     ` Nick Roberts
2008-07-08  7:06       ` Miles Bader
2008-07-08  7:18         ` Miles Bader
2008-07-08 23:39           ` Nick Roberts
2008-07-08 23:46             ` Miles Bader
2008-07-09 10:47               ` Nick Roberts [this message]
2008-07-15 13:37                 ` Miles Bader
2008-07-15 21:50                   ` Nick Roberts
2008-07-15 23:43                     ` Miles Bader
2008-07-05 14:04   ` Miles Bader
2008-07-05 16:11   ` Tom Tromey
2008-07-07  5:20     ` Nick Roberts
2008-07-07 14:40       ` Tom Tromey
2008-07-07 16:14         ` tomas
2008-07-07 19:33         ` David Hansen
2008-07-07 19:47           ` Lennart Borgman (gmail)
2008-07-07 20:01           ` Tom Tromey
2008-07-07 20:09             ` Lennart Borgman (gmail)
2008-07-07 23:11           ` Stephen J. Turnbull
2008-07-07 23:03             ` Lennart Borgman (gmail)
2008-07-08 16:02         ` James Cloos

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18548.38718.630083.307385@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=david.hansen@gmx.net \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).