GNU bug report logs -
#4375
23.1.50; can't kill killed gud buffer
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Thu, 10 Sep 2009 09:34:54 +0100
with message-id <4AA8BA2E.3020005 <at> tnei.co.uk>
and subject line Re: bug#4375: 23.1.50; can't kill killed gud buffer
has caused the Emacs bug report #4375,
regarding 23.1.50; can't kill killed gud buffer
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact help-debbugs <at> gnu.org
immediately.)
--
4375: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=4375
Emacs Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the emacs-pretest-bug <at> gnu.org mailing list.
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
Maybe associated with the other gdb error I have just reported.
If I run gud with --annotate=3
I get lots of pre-prompt and post-prompt output
(perhaps this is to be expected), I kill the process with a signals KILL
- off the pulldown menu) and if I then attempt to kill the *gud ...*
buffer I get the message
gdb-input: Buffer *gud-ipsa-scripted* has no process
and the buffer is not killed :-(
Robert
If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
`bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/home/robert/emacs/etc/DEBUG for instructions.
In GNU Emacs 23.1.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 2.16.1)
of 2009-09-08 on robert-laptop
Windowing system distributor `The X.Org Foundation', version 11.0.10600000
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_GB.UTF-8
value of $XMODIFIERS: nil
locale-coding-system: utf-8-unix
default enable-multibyte-characters: t
Major mode: Debugger
Minor modes in effect:
desktop-save-mode: t
recentf-mode: t
show-paren-mode: t
tooltip-mode: t
tool-bar-mode: t
mouse-wheel-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
global-auto-composition-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
line-number-mode: t
transient-mark-mode: t
--
Robert A J Marshall,
TNEI Services Ltd, 86-90 London Road, Manchester, M1 2PW
Registered in England & Wales No. 03891836,
Registered office: Milburn House, Dean Street, Newcastle upon Tyne, NE1 1LE
tel: +44 161 615 6017; fax: +44 161 615 6001; mobile: +44 7759 688384
web: http://IPSA-Power.com
[Message part 3 (message/rfc822, inline)]
works for me! (thanks)
Robert
--
Robert A J Marshall,
web: http://IPSA-Power.com
This bug report was last modified 15 years and 339 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.