Re: pure-fns in byte-opt.el

[Eli Zaretskii]

> Date: Thu, 27 Jul 2017 20:24:48 -0400
> From: Mark Oteiza <address@hidden>
> Cc: address@hidden, address@hidden
> 
> #0  0x00000000005eb363 in wrong_type_argument (predicate=XIL(0x8550), 
> value=XIL(0x3df5914)) at data.c:154
> #1  0x000000000065ed98 in exec_byte_code (bytestr=XIL(0x2d8cb34), 
> vector=XIL(0x17aec35), maxdepth=make_number(13), args_template=XIL(0), 
> nargs=0, args=0x0) at bytecode.c:512
>         op = 64
>         type = CATCHER
>         targets = 

Hmm... exec_byte_code directly above wrong_type_argument is a bit
unfortunate.  But let's try to see what we can:

> #3  0x000000000060f09b in Ffuncall (nargs=4, args=0x7fffffffb688) at 
> eval.c:2742
>         fun = XIL(0x17aee65)
>         original_fun = XIL(0x20b0da0)
>         funcar = XIL(0xce8cc0)
>         numargs = 3
>         val = make_number(897379714801469509)
>         count = 58

In this frame #3, what are the values of the important variables?

  (gdb) frame 3
  (gdb) pp original_fun
  (gdb) pp args[1]
  (gdb) pp args[2]
  (gdb) pp args[3]
  (gdb) pp fun
  (gdb) pp funcar

(If "pp" doesn't work, make sure src/.gdbinit was read by GDB.)