bug#56277: 29.0.50; Vterm crash after last git pull. Can be related to the 'abort-redisplay' patch?

[Eli Zaretskii <eliz@gnu.org>]

> Date: Tue, 28 Jun 2022 14:23:44 +0200
> From:  Vincenzo Pupillo via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Hi, today I pulled the latest changes and re-built emacs. But now vterm crash,
> just after invoked.
> The backtrace show that the vterm call thei own recenter function:
> 
> #10 0x00007fffbb19181d in recenter (env=env@entry=0x7fffffff8950,
>  pos=<optimized out>) at
>  /home/vincenzo/.emacs.d/elpa/vterm-20220613.1614/elisp.c:147
> 
> the corrisponding function is:
> void recenter(emacs_env *env, emacs_value pos) {
>   env->funcall(env, Frecenter, 1, (emacs_value[]){pos});
> }
> 
> Can be relate to "Merge branch 'abort-redisplay'" or  "Minor
> optimization of the "abort redisplay" feature" ?

Could be, although the changes introduced there don't do anything by
default, only if you customize a new variable.

The problem sounds like it's related to some memory allocation, and
the abort-redisplay feature didn't add any such allocations to the
code.

However, since I have no idea what vterm does, and from the backtrace
it sounds like it replaces some very low-level code in Emacs, such as
the implementation of recenter, I really cannot say.  Someone who
knows about vterm will have to debug this.