unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nick@nick.uklinux.net>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: gdbui hang
Date: Tue, 11 May 2004 22:07:31 +0100	[thread overview]
Message-ID: <16545.16531.713274.678978@nick.uklinux.net> (raw)
In-Reply-To: <87fza8qewy.fsf-monnier+emacs@gnu.org>

 > Add a kill-buffer-hook in the GUD buffer to kill the process (and the
 > related buffers).  Also add a check at the place where you select a buffer
 > that might be dead and if it's indeed dead clean things up as best you can.

Changing gud-kill-buffer-hook like this seems to work (gud-sentinel cleans
things up):

(defun gud-kill-buffer-hook ()
  (when (eq (current-buffer) gud-comint-buffer)
      (setq gud-minor-mode-type gud-minor-mode)
      (kill-process (get-buffer-process gud-comint-buffer))))

kill-process sends SIGKILL but I don't know why this kills the inferior (child
process of gdb) because SIGKILL doesn't do this if I run gdb from an xterm.

Shall I commit this change?

Nick

  reply	other threads:[~2004-05-11 21:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-10  4:43 gdbui hang Miles Bader
2004-05-10  6:22 ` Kim F. Storm
2004-05-10 17:30 ` Nick Roberts
2004-05-10 18:16   ` Stefan Monnier
2004-05-10 18:42     ` Nick Roberts
2004-05-11 12:23       ` Richard Stallman
2004-05-11 12:49       ` Miles Bader
2004-05-11 20:25         ` Nick Roberts
2004-05-11 21:08           ` Miles Bader
2004-05-11 21:27             ` Nick Roberts
2004-05-11 21:40             ` Stefan Monnier
2004-05-10 17:41 ` Nick Roberts
2004-05-10 19:09   ` Stefan Monnier
2004-05-11 21:07     ` Nick Roberts [this message]
2004-05-11 21:37       ` Stefan Monnier
2004-05-11 22:43         ` Nick Roberts
2004-05-11 23:23           ` Stefan Monnier
2004-05-12 12:40             ` Kim F. Storm
2004-05-12 14:59               ` Stefan Monnier

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=16545.16531.713274.678978@nick.uklinux.net \
    --to=nick@nick.uklinux.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).