unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Madhu <enometh@meer.net>
Cc: 36648-done@debbugs.gnu.org
Subject: bug#36648: emacs signals under gdb - [Re: connecting to a lost server process
Date: Fri, 19 Jul 2019 09:53:30 +0300	[thread overview]
Message-ID: <83v9vyv7kl.fsf@gnu.org> (raw)
In-Reply-To: <20190719.072339.546175785955923287.enometh@meer.net> (message from Madhu on Fri, 19 Jul 2019 07:23:39 +0530 (IST))

> Date: Fri, 19 Jul 2019 07:23:39 +0530 (IST)
> Cc: 36648@debbugs.gnu.org
> From: Madhu <enometh@meer.net>
> 
> > I suggest to use "M-x gdb", not "M-x gud-gdb".  The latter is an old
> > and semi-deprecated way of running GDB from Emacs.
> 
> [Unfortunately for me gud-gdb is the only way I can use gdb under
> emacs. I was using M-x gdb in emacs19, but was unable to use gdb under
> emacs for some time when it was replaced by gdb-mi - where it seemed a
> superhuman adversary would rearrange my windows and impede my workflow
> in myraid ways - until I discovered gud-gdb]

My suggestion is still to use "M-x gdb", but do that in a separate
frame.  Then the dedicated windows used by gdb-mi.el will not get in
the way of your other windows.

> > I guess we can close this bug report?
> 
> Yes please.

Thanks, done.





      reply	other threads:[~2019-07-19  6:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190712062057.15599.qmail@localhost.localdomain>
     [not found] ` <83r26v3cy3.fsf@gnu.org>
     [not found]   ` <mailman.985.1562918079.2688.help-gnu-emacs@gnu.org>
2019-07-14 12:00     ` bug#36648: emacs signals under gdb - [Re: connecting to a lost server process Madhu
2019-07-18  5:35       ` Eli Zaretskii
2019-07-18 14:58         ` Madhu
2019-07-18 15:24           ` Eli Zaretskii
2019-07-19  1:53             ` Madhu
2019-07-19  6:53               ` Eli Zaretskii [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=83v9vyv7kl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=36648-done@debbugs.gnu.org \
    --cc=enometh@meer.net \
    /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).