Re: gdb-ui, dedicated windows

[Nick Roberts <nickrob@snap.net.nz>]

 > > 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.
 > 
 > Why is this a problem?  In such cases, the source buffer should get
 > changed via gdb-display-source-buffer, which will update the associated
 > source-file, right?

It needs to distinguish between cases when it is appropriate to replace the
entire window with one displaying the new file, as described previously
and when it isn't, as in your example.

 > In other words, it seems that as long as gud is the one doing the
 > updating of the source window, everything will remain consistent, and it
 > will keep using that window.  It would only be if some external agent
 > changes what's displayed in that window that the state would become
 > inconsistent -- and in that case, it's probably the right thing to do to
 > pop up a new window (which will become the new source window).
 > 
 > Anyway, I can make the obvious change and see if it feels funny.

Sure.  If there are problems it can easily be reverted.  It might be a good
idea to start by not making the windows dedicated then perhaps David Hansen
can say if that cures his use case. 

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