|Subject:||Re: Unexec dumping results in "Segmentation fault" on Windows Msys2|
|Date:||Sun, 4 Apr 2021 11:41:33 +0300|
|User-agent:||Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0|
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'
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.
As for why am I even bothering with unexec - I started at noticing that compiling 26.3 no longer works with the newer Msys2 versions, though I was sure able to compile it before. Then I eventually tracked that it's unexec that's the problem and the reason 27 works is due to pdumper.
|[Prev in Thread]||Current Thread||[Next in Thread]|