From: Eli Zaretskii <eliz@gnu.org>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: schwab@suse.de, emacs-devel@gnu.org
Subject: Re: pure-fns in byte-opt.el
Date: Thu, 27 Jul 2017 20:06:18 +0300 [thread overview]
Message-ID: <83y3r94xo5.fsf@gnu.org> (raw)
In-Reply-To: <20170727023608.GA1895@holos.localdomain> (message from Mark Oteiza on Wed, 26 Jul 2017 22:36:08 -0400)
> Date: Wed, 26 Jul 2017 22:36:08 -0400
> From: Mark Oteiza <mvoteiza@udel.edu>
> Cc: schwab@suse.de, emacs-devel@gnu.org
>
> >If you could run the offending command under a debugger and show both
> >C-level and Lisp-level backtrace from the error, maybe we could become
> >wiser. (Let me know if you need help in staging the experiment and/or
> >collecting the data after you catch the error.)
>
> Here is the point during the build the error happens:
>
> "../../src/bootstrap-emacs" -batch --no-site-file --no-site-lisp -L . -l
> unidata-gen \
> -f unidata-gen-file ../../lisp/international/uni-decomposition.el .
> Loading macroexp.elc...
> Wrong type argument: listp, "頩"
>
> I set a breakpoint at wrong_type_argument
>
> Thread 1 "bootstrap-emacs" hit Breakpoint 4, wrong_type_argument (
> predicate=XIL(0x8550), value=XIL(0x3dee414)) at data.c:154
> 154 xsignal2 (Qwrong_type_argument, predicate, value);
> (gdb) xbacktrace
> "unidata-gen-table-word-list" (0xffffb690)
> "unidata-gen-table-decomposition" (0xffffbb20)
> "unidata-gen-file" (0xffffc108)
> "funcall" (0xffffc100)
> "if" (0xffffc2c0)
> "cond" (0xffffc430)
> "let*" (0xffffc5d0)
> "while" (0xffffc760)
> "let*" (0xffffc900)
> "progn" (0xffffca30)
> "if" (0xffffcb70)
> "let" (0xffffcd50)
> "let" (0xffffcf30)
> "command-line-1" (0xffffd0b0)
> "command-line" (0xffffd300)
> "unwind-protect" (0xffffd4f0)
> "let" (0xffffd6d0)
> "if" (0xffffd840)
> "normal-top-level" (0xffffd9c0)
>
> I would need help with digging deeper.
Is this still relevant, i.e. do you still want to understand the
details of the problem? If so, please show the C-level backtrace (the
result of the "bt" command), and I will try to tell you where to look
for those details.
Thanks.
next prev parent reply other threads:[~2017-07-27 17:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 2:06 pure-fns in byte-opt.el Mark Oteiza
2017-07-25 8:14 ` Andreas Schwab
2017-07-25 14:16 ` Stefan Monnier
2017-07-25 20:57 ` Philipp Stephani
2017-07-25 21:27 ` Stefan Monnier
2017-07-25 22:28 ` Clément Pit-Claudel
2017-07-26 0:08 ` Stefan Monnier
2017-07-26 7:39 ` Clément Pit-Claudel
2017-07-26 12:58 ` Stefan Monnier
2017-07-28 17:45 ` Philipp Stephani
2017-07-28 17:49 ` Stefan Monnier
2017-07-28 17:52 ` Philipp Stephani
2017-07-28 22:20 ` Stefan Monnier
2017-09-24 7:31 ` Philipp Stephani
2017-09-24 16:23 ` Stefan Monnier
2017-09-25 22:06 ` Richard Stallman
2017-09-26 0:25 ` Stefan Monnier
2020-07-25 19:53 ` Philipp Stephani
2020-07-25 19:58 ` Stefan Monnier
2020-07-25 20:08 ` Philipp Stephani
2020-07-25 20:59 ` Stefan Monnier
2020-07-29 14:21 ` Philipp Stephani
2020-07-29 14:25 ` Stefan Monnier
2017-09-24 16:26 ` Drew Adams
2017-07-26 1:00 ` Mark Oteiza
2017-07-26 14:33 ` Eli Zaretskii
2017-07-27 2:36 ` Mark Oteiza
2017-07-27 2:46 ` Stefan Monnier
2017-07-29 16:43 ` Mark Oteiza
2017-07-29 17:22 ` Eli Zaretskii
2017-07-29 19:48 ` Mark Oteiza
2017-07-29 20:03 ` Andreas Schwab
2017-07-29 20:14 ` Mark Oteiza
2017-07-27 17:06 ` Eli Zaretskii [this message]
2017-07-28 0:24 ` Mark Oteiza
2017-07-28 7:02 ` Eli Zaretskii
2017-07-29 1:24 ` Mark Oteiza
2017-07-29 7:24 ` Eli Zaretskii
2017-07-29 16:34 ` Mark Oteiza
2017-07-29 17:21 ` Eli Zaretskii
2017-09-24 7:34 ` Philipp Stephani
2017-09-24 16:24 ` Stefan Monnier
2017-09-24 23:22 ` John Wiegley
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=83y3r94xo5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mvoteiza@udel.edu \
--cc=schwab@suse.de \
/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.