unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
	Miles Bader <miles@gnu.org>
Subject: Re: gdbui hang
Date: Tue, 11 May 2004 17:08:54 -0400	[thread overview]
Message-ID: <20040511210854.GB8144@fencepost> (raw)
In-Reply-To: <16545.14031.598931.771041@nick.uklinux.net>

On Tue, May 11, 2004 at 09:25:51PM +0100, Nick Roberts wrote:
>  > The new gdbui mode seems to get wedged in these unrecoverable states way
>  > too often, and seems way too fragile... (with traditional gdb mode,
>  > hitting C-g a few times and then C-c C-c a few times was usually enough
>  > to get you back into some known state).
> 
> For each GDB command the user types, it runs several behind the users back to
> keep Emacs informed about the status of the program being debugged. This
> requires careful co-ordination and will take just take time to iron out the
> bugs. I can only suggest that you submit a bug report for each case.

Yes, I fully understand your dilemna, but the bugs in gdbui typically seem
pretty hard to describe in a useful way -- often it just hangs, and won't
unhang -- and are not easily repeatable.

Is there some internal state that be useful to quote in a bug report?  Even
better, how about a dump-gdbui-internal-state command that could be used
when sending a bug report?

Thanks,

-Miles
-- 
P.S.  All information contained in the above letter is false,
      for reasons of military security.

  reply	other threads:[~2004-05-11 21:08 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 [this message]
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
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=20040511210854.GB8144@fencepost \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).