unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: jonetsu <jonetsu@teksavvy.com>
To: help-gnu-emacs@gnu.org
Subject: Using gdb (windows popping up)
Date: Sun, 9 Jun 2019 11:52:46 -0400	[thread overview]
Message-ID: <20190609115246.41281b50@mistral> (raw)

Hello,

I'm trying to simply get a debug session going on in a minimal way that
is, gdb in one buffer (window) and the source in the other buffer
(window), both being displayed side by side.  Simple enough, and the
customize-variable gdb-show-main set to non-nil allows just for this to
happen.

The gdb session starts (M-x gdb) with on the left gdb and on the right
the source.  In the source a breakpoint can be placed in the margin.
All fine, looks very good...

... until the debugging session starts.  At which point emacs decides
to create a new whole emacs app/window with the source code in it.  It
boldly replaces the source window with the debugged app's output window
and throws the source into a new emacs instance.

But the source code was already displayed and a breakpoint was set in
it showing that it is active and linked to gdb.  Why do that ?  If you
really want to show the output window, why not split the gdb window ?
Or maybe totally forget about the output window until the user wants
it ?  

Or is there a variable or two to control this ?  I read through the
documentation and did not find anything so far.  I would just like to
establish a clean working state with emacs and gdb in which things are
not popping up unexpectedly in new instances of emacs.  Emacs version
is 26.1.  Speedbar is not used in this case.

Cheers.



             reply	other threads:[~2019-06-09 15:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 15:52 jonetsu [this message]
2019-06-09 16:09 ` Using gdb (windows popping up) jonetsu
2019-06-09 16:18   ` jonetsu
2019-06-09 16:58     ` jonetsu
2019-06-09 17:48       ` Óscar Fuentes
2019-06-09 18:31 ` Eli Zaretskii
2019-06-09 18:59   ` jonetsu
2019-06-09 19:13     ` Eli Zaretskii
2019-06-09 19:27       ` jonetsu
2019-06-09 19:33         ` Noam Postavsky
2019-06-09 19:48           ` jonetsu
2019-06-09 20:15             ` Noam Postavsky
2019-06-09 21:10               ` jonetsu
2019-06-09 22:36                 ` Óscar Fuentes
2019-06-10 13:33                   ` jonetsu
2019-06-10 13:44                     ` Óscar Fuentes
2019-06-10 14:00                       ` jonetsu
2019-06-10 15:44                         ` Eli Zaretskii
2019-06-10 18:52                           ` jonetsu

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=20190609115246.41281b50@mistral \
    --to=jonetsu@teksavvy.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).