Re: Unexec dumping results in "Segmentation fault" on Windows Msys2

[Eli Zaretskii]

> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Wed, 21 Apr 2021 21:19:45 +0300
> 
> The problem that's left is that the main branch crashes with unexec 
> dumping on first lisp file compilation ever since commit cddf85d256. The 
> backtraces for that I grabbed earlier:
> 
> https://gist.githubusercontent.com/sg2002/32ea64634a89e7b407f50e29b4ab5f7e/raw/aa0bcc517e1a4de733a9dc2678f8c45daefb95f9/gistfile1.txt
> 
> https://gist.githubusercontent.com/sg2002/d9cfaf1268973b20d66d79f5df575498/raw/06091019c1d30b863e6000fb642e09316d82a344/gistfile1.txt

Like I said before: this looks like infinite recursion that causes
stack overflow.  A Lisp-level backtrace could help.  Does "xbacktrace"
report anything interesting?  If not, the way to get the Lisp
backtrace is to go to each frame that calls Ffuncall and do this:

  (gdb) p args[0]
  (gdb) xsymbol