[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61847: debug-early-backtrace only works some of the time.
From: |
Eli Zaretskii |
Subject: |
bug#61847: debug-early-backtrace only works some of the time. |
Date: |
Wed, 01 Mar 2023 18:53:13 +0200 |
> Date: Wed, 1 Mar 2023 16:05:58 +0000
> Cc: monnier@iro.umontreal.ca, 61847@debbugs.gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> My main argument against cl-prin1 is that it's Lisp, and loading Lisp in
> early bootstrap is an uncertain, difficult process, as this bug shows.
My main point, which I evidently fail to drive home, is that we must
do that anyway, if we want these backtraces to show a reasonably
readable information.
> prin1 is _far_ from "infinitely useless". I've used it to good effect.
Yes, and when I was younger, I used MSDOS to good effect.
> cl-prin1 is not useful for printing compiled functions.
Then let's make it useful! That's the right direction, not falling
back to prin1.
> How about this suggestion: to fix the bug right now, we put prin1 back
> in, as it was in the original debug-early.el. When cl-prin1 has
> improved sufficiently, we then consider putting it back into
> debug-early.el?
No.
- bug#61847: debug-early-backtrace only works some of the time., (continued)
bug#61847: debug-early-backtrace only works some of the time., Stefan Monnier, 2023/03/01
bug#61847: debug-early-backtrace only works some of the time., Eli Zaretskii, 2023/03/01