all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Claus Fischer <claus.fischer@clausfischer.com>
Cc: 30044@debbugs.gnu.org
Subject: bug#30044: Emacs: Gud-mode: Debugging with gud: Window switching problem
Date: Tue, 09 Jan 2018 20:44:01 +0200	[thread overview]
Message-ID: <83y3l66ff2.fsf@gnu.org> (raw)
In-Reply-To: <20180109123311.klciuvflkdgm23pf@clausfischer.com> (message from Claus Fischer on Tue, 9 Jan 2018 13:33:11 +0100)

> Date: Tue, 9 Jan 2018 13:33:11 +0100
> From: Claus Fischer <claus.fischer@clausfischer.com>
> 
> A few years ago, I filed a bug about debugging unter Emacs with
> gud and gdb.
> 
> The problem is that often times when a halt at a breakpoint requires
> a source file to load, the source file replaces the *gud-something*
> buffer, which is extremely disruptive to the work flow. One expects
> to continue typing in gud but finds oneself instead typing into some
> source file buffer.

How do you invoke GDB?  Is it "M-x gdb RET" or "M-x gud-gdb RET"?  I
suggest to try the former, and if you already do that, try the command
"M-x gdb-many-windows RET" after the debugging session starts.  I also
suggest to start the debugger in a separate frame, and switch to the
original frame when you want to work on your windows you had before
starting the debugging session.





  reply	other threads:[~2018-01-09 18:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 12:33 bug#30044: Emacs: Gud-mode: Debugging with gud: Window switching problem Claus Fischer
2018-01-09 18:44 ` Eli Zaretskii [this message]
2018-01-09 20:58   ` Claus Fischer
2018-01-10  3:28     ` Eli Zaretskii
2018-01-10  3:39 ` Noam Postavsky
2018-01-10 11:19   ` Claus Fischer
2018-01-11  1:58     ` Noam Postavsky
2018-01-11 13:24       ` Claus Fischer
2018-01-12  1:24         ` Noam Postavsky
2018-05-20 23:52 ` Noam Postavsky

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=83y3l66ff2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=30044@debbugs.gnu.org \
    --cc=claus.fischer@clausfischer.com \
    /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.