Re: pure-fns in byte-opt.el

[Mark Oteiza]

On 27/07/17 at 08:06pm, Eli Zaretskii wrote:
> > Date: Wed, 26 Jul 2017 22:36:08 -0400
> > From: Mark Oteiza <address@hidden>
> > Cc: address@hidden, address@hidden
> >
> > >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
> > <snip>
> >
> > 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.

Yes, I'd like to better understand what is going on here.  Looking at
Fmake_vector and read_vector, I see that calling make-vector and reading
a literal vector do very different things, but how this ultimately
results in the error is not obvious to me.

btfull.txt
Description: Text document