From: John Wiegley <jwiegley@gmail.com>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org, Phillip Lord <phillip.lord@russet.org.uk>
Subject: Re: Debugging Emacs
Date: Sun, 29 Nov 2015 11:25:22 -0800 [thread overview]
Message-ID: <m2wpt0r4kd.fsf@newartisans.com> (raw)
In-Reply-To: <86k2p0vfl0.fsf@stephe-leake.org> (Stephen Leake's message of "Sun, 29 Nov 2015 12:13:47 -0600")
>>>>> Stephen Leake <stephen_leake@stephe-leake.org> writes:
> phillip.lord@russet.org.uk (Phillip Lord) writes:
>> Now, if we had a command, say `break', implemented in C, then added a
>> "breakpoint Fbreak" into .gdbinit, then all of this would happen
>> automatically. Under GDB, then "M-x break" or (break) Emacs would halt.
>> Outside M-x break would do nothing.
> I would find this convenient; I would not have to remember what function I
> had set a break in for my current debug session; it would always be the same
> one.
I would also like this. I've injected similar "debug hooks" into other
products before, and it is most helpful.
John
next prev parent reply other threads:[~2015-11-29 19:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 17:23 Debugging Emacs Phillip Lord
2015-11-27 17:48 ` Karl Fogel
2015-11-27 21:53 ` Phillip Lord
2015-11-28 7:50 ` Eli Zaretskii
2015-11-27 17:58 ` Eli Zaretskii
2015-11-27 18:15 ` Eli Zaretskii
2015-11-27 22:05 ` Phillip Lord
2015-11-28 7:56 ` Eli Zaretskii
2015-11-28 19:39 ` Phillip Lord
2015-11-28 20:38 ` Eli Zaretskii
2015-11-28 21:35 ` Phillip Lord
2015-11-29 18:13 ` Stephen Leake
2015-11-29 19:25 ` John Wiegley [this message]
2015-11-29 21:26 ` Phillip Lord
2015-11-29 19:46 ` Marcin Borkowski
2015-11-30 13:33 ` Nicolas Richard
2015-12-05 10:55 ` Eli Zaretskii
2015-12-07 9:51 ` Phillip Lord
2015-12-07 16:34 ` Eli Zaretskii
2015-12-07 18:18 ` Stephen Leake
2015-12-07 18:30 ` Eli Zaretskii
2015-12-10 22:36 ` Phillip Lord
2015-12-11 7:39 ` Eli Zaretskii
2015-12-11 15:47 ` Phillip Lord
2015-11-28 8:41 ` Marcin Borkowski
2015-11-28 9:47 ` 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=m2wpt0r4kd.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
--cc=stephen_leake@stephe-leake.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).