From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: [PATCH]: Re: Early backtrace.
Date: Fri, 04 Feb 2022 16:02:56 +0200 [thread overview]
Message-ID: <83h79e3f1r.fsf@gnu.org> (raw)
In-Reply-To: <jwv8ruqdajl.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 04 Feb 2022 08:31:25 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: acm@muc.de, emacs-devel@gnu.org
> Date: Fri, 04 Feb 2022 08:31:25 -0500
>
> > How about adding to debug-early.el some minimal documentation, which
> > would explain how to use this facility for debugging bootstrap
> > problems and batch-mode problems in general?
>
> AFAIK there is nothing for the user to do to "use this facility".
> It's already automatically used when the normal debugger can't be used.
That's not explained there, either. Including what exactly hides
behind "when the normal debugger can't be used" part.
next prev parent reply other threads:[~2022-02-04 14:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 20:34 Early backtrace Alan Mackenzie
2022-01-10 21:54 ` Stefan Monnier
2022-01-11 11:36 ` Alan Mackenzie
2022-01-11 14:47 ` Stefan Monnier
2022-01-30 11:07 ` [PATCH]: " Alan Mackenzie
2022-01-30 16:31 ` Stefan Monnier
2022-01-31 14:04 ` Stefan Monnier
2022-02-01 19:14 ` Alan Mackenzie
2022-02-02 3:36 ` Stefan Monnier
2022-02-02 20:38 ` Alan Mackenzie
2022-02-02 20:59 ` Stefan Monnier
2022-02-03 8:38 ` Eli Zaretskii
2022-02-03 21:35 ` Alan Mackenzie
2022-02-04 7:24 ` Eli Zaretskii
2022-02-04 21:01 ` Alan Mackenzie
2022-02-05 7:12 ` Eli Zaretskii
2022-02-05 10:48 ` Alan Mackenzie
2022-02-04 13:31 ` Stefan Monnier
2022-02-04 14:02 ` Eli Zaretskii [this message]
2022-01-31 9:30 ` Philipp Stephani
2022-01-31 12:42 ` Eli Zaretskii
2022-01-31 16:54 ` Alan Mackenzie
2022-01-31 17:24 ` Alan Mackenzie
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=83h79e3f1r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.