unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Debugging Emacs
Date: Sat, 28 Nov 2015 19:39:38 +0000	[thread overview]
Message-ID: <878u5hlxqd.fsf@russet.org.uk> (raw)
In-Reply-To: <83h9k6r1z8.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 28 Nov 2015 09:56:43 +0200")

Eli Zaretskii <eliz@gnu.org> writes:
>> Yes, that was sort of the idea. Personally, I'd not be too worried about
>> repeating things. I realise that this adds to the maintainance burden,
>> but references to later sections make for harder reading.
>
> It is OK to say something simple in the preamble, and refer to later
> sections for more in-depth detail.
>
> But I will now stop writing comments to a text I didn't yet see, and
> let you work on it instead ;-)


It was at the bottom of the original email!

While I am mailing, I had one idea which might simplify debugging.
Currently, you need to break-point some function to get control to GDB
before you launch Emacs. Why not add a null function to Emacs core for
the purpose? Guaranteed never to be called from anywhere, does nothing,
and with a breakpoint could be added to .gdbinit. Then, after running
Emacs, "M-x break" would automatically pass control back to GDB without
any further set up.

Just a thought.

Phil




  reply	other threads:[~2015-11-28 19:39 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 [this message]
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
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=878u5hlxqd.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --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).