unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Welsh Duggan <md5i@cs.cmu.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Simultaneous gdb session badness
Date: Fri, 19 Aug 2005 00:59:03 -0400	[thread overview]
Message-ID: <87br3u34ko.fsf@cs.cmu.edu> (raw)
In-Reply-To: <17156.17099.88084.969378@farnswood.snap.net.nz> (Nick Roberts's message of "Thu, 18 Aug 2005 20:11:55 +1200")

Nick Roberts <nickrob@snap.net.nz> writes:

> Michael Welsh Duggan writes:
>  > Yes, I see that now.  It was not obvious from NEWS, so I didn't
>  > realize I needed to reread the gdb manual.  (I remember reading the
>  > messages covering bits of this on emacs-devel now that you brought
>  > this up, but I obviously didn't read them closely enough.)
>
> The old behaviour has not changed.  Perhaps NEWS should say that the new
> behaviour is the default now.  (The extract that I posted earlier was from
> the Emacs manual and *not* the gdb manual.  Which NEWS did you read?)

I should have said the gdb section of the Emacs manual.

>  > More importantly though, if one cannot run multiple sessions without
>  > using --fullname, M-x gdb should not allow you to attempt to so.  It
>  > would be much better for it to give an understandable error message
>  > letting the user know what is going on.
>
> Sure.  The problem is that Emacs has to start running gdb and receive some
> output before it knows whether its working in text mode or graphical mode.
> Currently the GUD buffer is created before gdb is run.

I would take that.  It would catch the majority of cases, I think.
You'd have to start two sessions at very nearly exactly the same time
for the second to start before the first produced any output, I would
think.

-- 
Michael Welsh Duggan
(md5i@cs.cmu.edu)

      reply	other threads:[~2005-08-19  4:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 20:53 Simultaneous gdb session badness Michael Welsh Duggan
2005-08-16 21:20 ` Nick Roberts
2005-08-18  5:36   ` Michael Welsh Duggan
2005-08-18  8:11     ` Nick Roberts
2005-08-19  4:59       ` Michael Welsh Duggan [this message]

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=87br3u34ko.fsf@cs.cmu.edu \
    --to=md5i@cs.cmu.edu \
    --cc=emacs-devel@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).