unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alain Schneble <a.s@realize.ch>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Debugging GNU Emacs on MS Windows / getting control back to gdb
Date: Sun, 21 Aug 2016 18:38:57 +0200	[thread overview]
Message-ID: <86lgzqjcv2.fsf@realize.ch> (raw)
In-Reply-To: <83wpjaayfs.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 21 Aug 2016 19:17:43 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Alain Schneble <a.s@realize.ch>
>> Date: Sun, 21 Aug 2016 18:09:57 +0200
>> 
>> When debugging GNU Emacs using gdb or gud-gdb on MS Windows, is there a
>> way to return control back to GDB at any point in time by suspending the
>> debuggee process -- without setting any breakpoint upfront?
>
> Not really, no.
>
> But what's the problem of setting a breakpoint up front?

I just wanted to step through `Fappend'.  But it's called a lot.  It
would have been much easier to just arrange for the state manually, then
suspend, set the breakpoint in Fappend and eval my elisp function that
calls the Fappend I'm interested in.  That sounded much easier to me
than configuring proper conditions on the breakpoint.  As an
alternative, I could have put a breakpoint on a rarly called function
such as Fredraw_display, as suggested in ./etc/DEBUG.  But that felt
more like a workaround as well.  Or is there yet another (better)
approach?

Thanks.
Alain




  reply	other threads:[~2016-08-21 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21 16:09 Debugging GNU Emacs on MS Windows / getting control back to gdb Alain Schneble
2016-08-21 16:17 ` Eli Zaretskii
2016-08-21 16:38   ` Alain Schneble [this message]
2016-08-21 18:43     ` Eli Zaretskii
2016-08-21 19:06       ` Alain Schneble
2016-08-21 19:16         ` Eli Zaretskii
2016-08-21 16:46   ` Alain Schneble
2016-08-21 18:52     ` Eli Zaretskii
2016-08-21 19:08       ` Alain Schneble
2016-08-21 19:17         ` Eli Zaretskii
2016-08-21 19:23           ` Alain Schneble

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=86lgzqjcv2.fsf@realize.ch \
    --to=a.s@realize.ch \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).