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 21:06:36 +0200 [thread overview]
Message-ID: <86d1l2j60z.fsf@realize.ch> (raw)
In-Reply-To: <83tweearpg.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 21 Aug 2016 21:43:07 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Alain Schneble <a.s@realize.ch>
>> Date: Sun, 21 Aug 2016 18:38:57 +0200
>> Cc: emacs-devel@gnu.org
>>
>> 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.
>
> It's not a workaround, it's the real thing.
Ok.
> And even that might not be enough for a frequently called function.
> Then you need to make the breakpoint conditional on some input values,
> or the value of point, or whatever else can filter out hits you don't
> want.
But that was exactly my point, that it is more cumbersome to setup a
conditional breakpoint. Whereas with a process suspension, I only have
to set an unconditional breakpoint and then continue execution. Of
course, this works well only if I know that the next call to the
function is the one call I'm interested in.
next prev parent reply other threads:[~2016-08-21 19:06 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
2016-08-21 18:43 ` Eli Zaretskii
2016-08-21 19:06 ` Alain Schneble [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86d1l2j60z.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 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.