From: Paul K <mafeuser@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: emacs 24.4.1, gud-gdb, problem: at breakpoint hit, *gud* buffer is replaced with source code buffer
Date: Tue, 17 Feb 2015 16:22:00 +0100 [thread overview]
Message-ID: <CAA+mFXOh=UeuZa5ZYvQTjH8hGTmryD_=fFtZP1DfAnLNSh29Og@mail.gmail.com> (raw)
Hallo people.
I'm debugging C++ files with M-x gud-gdb.
I set the breakpoint is some source file.
*gud-gdb* occupies one half (top or bottom) of frame, while source buffer
occupies other one.
Then I visit another source file and another....
Now I start the program or just rerun it from *gud-procname* window and
when breakpoint is hit, SOMETIMES emacs visits the source file in
*gud-procname* window, while it should visit it in another one, so that to
prevent *gud-procname* from disappearing.
Have You got any idea what might be the reason?
If not, could You please tell me where to hook with edebug-defun?
best regards,
Mattt
next reply other threads:[~2015-02-17 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 15:22 Paul K [this message]
2015-02-18 15:08 ` emacs 24.4.1, gud-gdb, problem: at breakpoint hit, *gud* buffer is replaced with source code buffer Paul K
2015-02-18 15:45 ` Eli Zaretskii
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='CAA+mFXOh=UeuZa5ZYvQTjH8hGTmryD_=fFtZP1DfAnLNSh29Og@mail.gmail.com' \
--to=mafeuser@gmail.com \
--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.
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).