Re: transpose-regions

[Chong Yidong <cyd@stupidchicken.com>]

martin rudalics <rudalics@gmx.at> writes:

> Breakpoint 3, Fsignal (error_symbol=23761593, data=33053189) at eval.c:1620
> (gdb) up 4
> #4  0x0107e521 in Flength (sequence=35211917) at fns.c:185
> (gdb) p sequence
> $1 = 35211904
> (gdb) xtype
> Lisp_Int
> (gdb) xsymbol
> $2 = (struct Lisp_Symbol *) 0x2194a80
> 0

That implies that in fns.c:607:concat, the value of args[0], which is
the argument passed to Flength, is 35211917, a Lisp integer.

However, this makes no sense, because just a few lines above that, we
check the type of arg[0]:

  for (argnum = 0; argnum < nargs; argnum++)
    {
      this = args[argnum];
      if (!(CONSP (this) || NILP (this) || VECTORP (this) || STRINGP (this)
	    || COMPILEDP (this) || BOOL_VECTOR_P (this)))
	wrong_type_argument (Qsequencep, this);
    }

So could you please check that in frame 5, argnum is indeed 0 and
args[0] is 35211917, and check the xtype of args[0] in that frame?