From: Claus Fischer <claus.fischer@clausfischer.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30044@debbugs.gnu.org
Subject: bug#30044: Emacs: Gud-mode: Debugging with gud: Window switching problem
Date: Tue, 9 Jan 2018 21:58:47 +0100 [thread overview]
Message-ID: <20180109205847.7nalpvfhula5ehmz@clausfischer.com> (raw)
In-Reply-To: <83y3l66ff2.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2006 bytes --]
On Tue, Jan 09, 2018 at 08:44:01PM +0200, Eli Zaretskii wrote:
> > 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.
I do
M-x gud-gdb RET
since I found the other not to work as I like; a few years ago, I
started it as M-x gdb but then something changed - I don't remember
what - and I changed to gud-gdb. What's the difference? I just tried
it, I think it's the separate i/o window, isn't it?
If so, I'll stick with gud-gdb. I want my debugging session in a
single frame, and stdio is not relevant for my programs.
I usually have many frames open, but gdb is started in just one, and
when it encounters a breakpoint, it splits the frame, and that suits
me just fine - except for it sometimes burying the gud window itself.
I don't think the behavious depends on there being multiple frames.
Is that what you are suggesting?
It's hard to reproduce, but it's annoying nevertheless. I do a lot of
work in the setting emacs - autoconf - gcc - gdb, and it's generally
very productive for work on server code.
Best regards,
Claus
--
Claus Fischer <claus.fischer@clausfischer.com>
http://www.clausfischer.com/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2018-01-09 20:58 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
2018-01-09 20:58 ` Claus Fischer [this message]
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=20180109205847.7nalpvfhula5ehmz@clausfischer.com \
--to=claus.fischer@clausfischer.com \
--cc=30044@debbugs.gnu.org \
--cc=eliz@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 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.