From: Nick Roberts <nickrob@snap.net.nz>
Cc: Klaus Zeitler <kzeitler@lucent.com>, emacs-devel@gnu.org
Subject: Re: gdb with many windows: kill associated buffers doesn't always work
Date: Wed, 24 May 2006 00:53:21 +1200 [thread overview]
Message-ID: <17523.1473.953618.707854@kahikatea.snap.net.nz> (raw)
In-Reply-To: <je64jwly56.fsf@sykes.suse.de>
> > If GDB crashes then thats a bug in GDB and this should rarely happen.
>
> But it happens, and when it happens you don't want to lose all your
> valuable history.
Well, if its that valuable you could presumably save it with 'set logging on'.
>...
> > Which two buffers?? The first one i.e the GUD buffer with the killed
> > process, and the second one i.e the one that can be invoked because the
> > current code only complains about multiple debugging when the gdb process
> > is still running.
>
> I still don't see where the second buffer appears when it is reused.
Sorry, I'm thinking of the case where GDB is invoked with a different
executable on the second occasion (although there are problems even when
the executable is the same, as Klaus pointed out).
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-05-23 12:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 7:21 gdb with many windows: kill associated buffers doesn't always work Klaus Zeitler
2006-05-23 9:29 ` Nick Roberts
2006-05-23 10:07 ` Klaus Zeitler
2006-05-23 10:31 ` Nick Roberts
2006-05-24 5:58 ` Klaus Zeitler
2006-05-23 11:24 ` Andreas Schwab
2006-05-23 11:55 ` Nick Roberts
2006-05-23 12:12 ` Andreas Schwab
2006-05-23 12:24 ` Nick Roberts
2006-05-23 12:32 ` Andreas Schwab
2006-05-23 12:53 ` Nick Roberts [this message]
2006-05-23 12:58 ` Andreas Schwab
2006-05-23 14:17 ` Stefan Monnier
2006-05-23 21:26 ` Nick Roberts
2006-05-24 10:15 ` Klaus Zeitler
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=17523.1473.953618.707854@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@gnu.org \
--cc=kzeitler@lucent.com \
/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).