all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Marshall <robert.marshall@tnei.co.uk>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-pretest-bug@gnu.org, 4375@emacsbugs.donarmstrong.com
Subject: bug#4375: 23.1.50; can't kill killed gud buffer
Date: Wed, 09 Sep 2009 08:22:28 +0100	[thread overview]
Message-ID: <4AA757B4.7090204@tnei.co.uk> (raw)
In-Reply-To: <19110.57126.832288.236368@totara.tehura.co.nz>

Nick Roberts wrote:
>  > 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 :-(
>
>  That does seem to be a bug, I have a look at it.  However, Emacs 23.1.50
>  should run GDB using GDB/MI (gdb -i=mi) not annotations (gdb --annotate=3)
>  so you shouldn't see any pre-prompt and post-prompt output.  I don't know
>  if you've customized gud-gdb-command-name or if your're manually editing
>  in the mini-buffer but you need to start with something like:
>
>  Run gdb (like this): gdb -i=mi yourprog
>
>  and you shouldn't need to kill the debugger.  Note that to stop the 
inferior
>  (program being debugged) you use C-c C-c (comint-interrupt-subjob) which
>  is signals BREAK on the pulldown menu.
>
>
>  > ...
>  > In GNU Emacs 23.1.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 2.16.1)
>  >  of 2009-09-08 on robert-laptop
>
Looks as if my earlier bug report hasn't appeared (the other bug was why 
I was trying --annotate)
If I run with -i=mi I get lots of

    mi_cmd_stack_info_frame: No arguments required
messages. Also if I try turning on tooltips when I hold the mouse over a 
variable I get the message

    error in process filter: Args out of range: "", 0, -1
There's also a longish wait on startup when it is turning off non stop mode
and I see the message there
    No symbol "non" in current context.
in the gdb buffer, I don't know if that is expected?

If I then do a quit in the debugger I also get the message about the 
process not running.

Robert

-- 
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






  reply	other threads:[~2009-09-09  7:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AA8BA2E.3020005@tnei.co.uk>
2009-09-08 15:08 ` bug#4375: 23.1.50; can't kill killed gud buffer Robert Marshall
2009-09-08 22:48   ` Nick Roberts
2009-09-09  7:22     ` Robert Marshall [this message]
2009-09-09  9:12       ` Nick Roberts
2009-09-09 10:41         ` Jan D.
2009-09-09 11:13           ` Nick Roberts
2009-09-09 14:41             ` Stefan Monnier
2009-09-09 21:55               ` Nick Roberts
2009-09-10  3:29                 ` Stefan Monnier
2009-09-10  4:13                   ` Nick Roberts
2009-09-10  9:04                     ` Jan D.
2009-09-10  9:09                       ` Jan D.
2009-09-10  8:57                 ` Jan D.
2009-09-10 10:03                   ` Nick Roberts
2009-09-10  3:09       ` Nick Roberts
2009-09-10  8:36         ` Robert Marshall
2009-09-10  3:49   ` Nick Roberts
2009-09-10  9:09     ` Robert Marshall
2009-09-10 10:08       ` Nick Roberts
2009-09-10 14:28         ` Robert Marshall
2009-09-10 21:37           ` Nick Roberts
2009-09-11 13:24             ` Robert Marshall
2009-09-10  8:45   ` bug#4375: marked as done (23.1.50; can't kill killed gud buffer) Emacs bug Tracking System

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

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

  git send-email \
    --in-reply-to=4AA757B4.7090204@tnei.co.uk \
    --to=robert.marshall@tnei.co.uk \
    --cc=4375@emacsbugs.donarmstrong.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=nickrob@snap.net.nz \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.