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: Re: Using gdb (windows popping up)
Date: Mon, 10 Jun 2019 10:00:45 -0400	[thread overview]
Message-ID: <20190610100045.61c22fe0@mistral> (raw)
In-Reply-To: <87a7eptv1a.fsf@telefonica.net>

On Mon, 10 Jun 2019 15:44:01 +0200
Óscar Fuentes <ofv@wanadoo.es> wrote:

> Even if what you see is everything that counts for you, the definition
> of "instance" that you use is not correct, because you can change what
> you see on frame1 while operating from frame2.

Of course, it can be re-ordered.  The thing is, though, is this overhead
worthwhile to do at the beginning of each debugging session ?  What are
the benefits towards the work being done ?

Especially in the light that the M-x gdb session actually starts with
the gdb interactive buffer and source /automatically/ placed
side-by-side by emacs.  ... Only to be disrupted with the source thrown
into another frame as soon as the debugging session starts.




  reply	other threads:[~2019-06-10 14:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 15:52 Using gdb (windows popping up) jonetsu
2019-06-09 16:09 ` 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 [this message]
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=20190610100045.61c22fe0@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).