bug#48252: Crashes continue ...

[Eli Zaretskii]

[Please use Reply All to reply, to keep the bug address CC'ed.]

> From: andrei.elkin@pp.inet.fi
> Date: Fri, 29 Oct 2021 20:19:40 +0300
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: andrei.elkin@pp.inet.fi
> >> Cc: 48252@debbugs.gnu.org
> >> Date: Fri, 29 Oct 2021 18:08:03 +0300
> >> 
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >> 
> >> >> From: andrei.elkin@pp.inet.fi
> >> >> Date: Thu, 28 Oct 2021 16:38:00 +0300
> >> >> 
> >> >> ...and what maybe is better that the most recent stack, below, is much 
> >> >> shorter.
> >> >> And I am leaving it alive in case there will be interest or just further
> >> >> instruction for me.
> >> >
> >> > Please invoke xbacktrace and post the results.  (If GDB says it
> >> > doesn't know that command, say "source /path/to/emacs/src/.gdbinit"
> >> > first.)
> >> 
> >> (gdb) xbacktrace 
> >> "command-error-default-function" (0xffffd448)
> >> "apply" (0xffffd618)
> >> 0xea3950a0 PVEC_COMPILED
> >
> > Is that all?  It should be a lot longer.
> 
> That's all though bt still produces the same stack.

I've re-read the discussion till now, and I'm afraid this crash
provides no new information that can allow us to make progress.  Once
again, Emacs tries to signal an error, and the error data includes
some invalid object.

As I said earlier, the only way forward is to come up with a
reproducible recipe starting from "emacs -Q", so that I or someone
else could debug it locally.

Or maybe you could figure out which Lisp code is running when this
happens, and show the problematic Lisp.

Sorry I couldn't be of more help.