From: Madhu <enometh@meer.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Running gdb in emacs.
Date: Fri, 17 Jan 2020 14:42:53 +0530 [thread overview]
Message-ID: <m3r1zyjvje.fsf@leonis4.robolove.meer.net> (raw)
In-Reply-To: mailman.2731.1579187331.1979.help-gnu-emacs@gnu.org
* Eli Zaretskii <mailman.2731.1579187331.1979.help-gnu-emacs@gnu.org> :
Wrote on Thu, 16 Jan 2020 17:09:03 +0200:
> "M-x gud-gdb" is the old way of running GDB under Emacs. It relies on
> a GDB feature, called "annotations", which is deprecated by the GDB
> developers, and could be removed from GDB at any moment.
>
> "M-x gdb" with all its features was written to be the main method of
> running GDB from Emacs. We suggest that you use only "M-x gdb",
> unless you have a very good reason, like some version of GDB that
> doesn't support the mi interface well.
I know you've given me advice before and I did try gdb-mi again, but it
I fint it is still unusable. I can think of two reasons:
1. I am limited to using 80column frames and the windows that gdb-mi are
too small and their content cannot be viewed without too navigating
through too many keystrokes - repeated at every `step'
2. I prefer to use display-buffer-reuse-window when possible for
display-buffer. When stepping through functions which are spread out in
different files I need to have all the files open at specific points
(i'm trying to understand the code). Every `step' alters the window
configuration that I expect and I spend more time in getting back to
where I was before invoking the gdb action, than actually debugging.
On the other hand gud-gdb is more managable. With annotations it also
pops to the buffer with the annotated source line (when available) but
the overall disruption is much less.
prev parent reply other threads:[~2020-01-17 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 9:27 Running gdb in emacs aprekates
2020-01-16 15:09 ` Eli Zaretskii
[not found] ` <mailman.2731.1579187331.1979.help-gnu-emacs@gnu.org>
2020-01-17 9:12 ` Madhu [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r1zyjvje.fsf@leonis4.robolove.meer.net \
--to=enometh@meer.net \
--cc=help-gnu-emacs@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.