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

[Eli Zaretskii <eliz@gnu.org>]

> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Sun, 4 Apr 2021 11:41:33 +0300
> 
> Yeah, I know about GDB, but was thinking that someone with more 
> experience than me at debugging such issues would be able to 
> independently confirm this. I'll try GDB eventually and report my findings.

It's very inefficient (read: impractical) to debug this kind of
problems remotely.  And I wouldn't hold my breath expecting people to
build the unexec version.

> The second crash happened for unexec, it seems like (some) pdumper code 
> was getting built there. I can confirm that your commit fixed unexec at 
> least to the point that I'm getting the same segfault now. Another issue 
> with master I just ran into is:
> 
> D:/Emacs/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: 
> image.o:image.c:(.text+0x7307): undefined reference to 
> `rsvg_handle_set_stylesheet'
> D:/Emacs/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: 
> image.o:image.c:(.text+0x73d7): undefined reference to 
> `rsvg_handle_set_stylesheet'

This should be fixed now.  Alan, please remember the WINDOWSNT aspect
when you add calls to RSVG functions never used before.  We had this
discussion in the past, I believe.

> Doing --without-rsvg works. The current msys2 rsvg version is 
> librsvg-2.50.3-1. Looks like possible fallout from #44065, since a 
> similar result was reported there.

No, because that change was never committed.  It's a new problem,
since yesterday.