From: Jarek Czekalski <jarekczek@poczta.onet.pl>
To: 15789@debbugs.gnu.org
Subject: bug#15789: 24.3.50; backtrace produces unreadable output
Date: Sat, 02 Nov 2013 09:54:35 +0100 [thread overview]
Message-ID: <5274BDCB.4090100@poczta.onet.pl> (raw)
This is the code I use to produce an example backtrace:
(defadvice tmm-add-prompt (before emacspeak pre act comp)
"Speaks the list of completions we have available."
(backtrace))
Then launch M-x tmm-menubar to have it output the backtrace.
When I test it on Emacs 23.4, I have a nice backtrace output, with one
readable line per stack item. On r114884 this looks really ugly,
unreadable. Some bytecode lines are mixed with words.
The stack trace looks as though the compiled-function lisp type is
printed, so I suspect that specbinding.bt.function changed its type,
which also affects Vsignaling_function argument to
command-error-function. I propose documenting the Lisp type of this
structure member.
In GNU Emacs 24.3.50.4 (i686-pc-linux-gnu, GTK+ Version 3.8.4)
of 2013-11-01 on jcdeb
Bzr revision: 114884 rgm@gnu.org-20131031213910-3509l9e973ne3zy1
Windowing system distributor `The X.Org Foundation', version 11.0.11204000
System Description: Debian GNU/Linux testing (jessie)
Important settings:
value of $LC_ALL: en_US
value of $LANG: pl_PL
locale-coding-system: iso-latin-1-unix
default enable-multibyte-characters: t
Major mode: Messages
Minor modes in effect:
tooltip-mode: t
mouse-wheel-mode: t
tool-bar-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
buffer-read-only: t
line-number-mode: t
transient-mark-mode: t
Recent input:
C-x C-f / j a r e k / l a n g / g n u / e m a c s p
e / t <backspace> <backspace> <tab> t m m <tab> <return>
M-x e v a l - b <tab> <return> M-` <escape> <escape>
<escape> C-x C-b <down> <f6> C-x o <down> <down> <return>
<prior> <next> <prior> <prior> <prior> <f11> <f11>
<up> <up> <up> M-x t o g g l e - t r u <tab> <return>
<home> <next> <prior> <prior> <prior> M-x r e p o r
t <tab> <return>
Recent messages:
[very long, removed intentionally by the reporter]
Load-path shadows:
None found.
Features:
(shadow sort gnus-util mail-extr emacsbug message format-spec rfc822 mml
mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231 mailabbrev
gmm-utils mailheader sendmail rfc2047 rfc2045 ietf-drums mm-util
mail-prsvr mail-utils help-mode easymenu tmm electric advice help-fns
time-date tooltip ediff-hook vc-hooks lisp-float-type mwheel x-win x-dnd
tool-bar dnd fontset image regexp-opt fringe tabulated-list newcomment
lisp-mode prog-mode register page menu-bar rfn-eshadow timer select
scroll-bar mouse jit-lock font-lock syntax facemenu font-core frame cham
georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao
korean japanese hebrew greek romanian slovak czech european ethiopic
indian cyrillic chinese case-table epa-hook jka-cmpr-hook help simple
abbrev minibuffer nadvice loaddefs button faces cus-face macroexp files
text-properties overlay sha1 md5 base64 format env code-pages mule
custom widget hashtable-print-readable backquote make-network-process
dbusbind gfilenotify dynamic-setting system-font-setting
font-render-setting move-toolbar gtk x-toolkit x multi-tty emacs)
next reply other threads:[~2013-11-02 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 8:54 Jarek Czekalski [this message]
2013-11-03 0:48 ` bug#15789: 24.3.50; backtrace produces unreadable output Stefan Monnier
2016-03-04 14:23 ` Lars Ingebrigtsen
2017-02-22 4:44 ` npostavs
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=5274BDCB.4090100@poczta.onet.pl \
--to=jarekczek@poczta.onet.pl \
--cc=15789@debbugs.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).