[Bug 49508] New: Powershell 6.* (pwsh.exe) crashes at start (regression)
https://bugs.winehq.org/show_bug.cgi?id=49508 Bug ID: 49508 Summary: Powershell 6.* (pwsh.exe) crashes at start (regression) Product: Wine Version: 5.11 Hardware: x86 URL: https://github.com/PowerShell/PowerShell/releases/down load/v6.1.6/PowerShell-6.1.6-win-x64.msi OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: Debian Created attachment 67636 --> https://bugs.winehq.org/attachment.cgi?id=67636 screenshot of error Did regression test, that showed 3533605293e8083dae19c5fbd41e2077faf5adc6 is the first bad commit but reverting that patch on top of wine from last monday didn`t help. So probably false alarm (?) In fact there seemed to be 2 regressions (one at end of the installer crashing) and this one which complicated regression test. That installer crash seems to be fixed now AFAICT. For now I just file this bug, and I think I`ll do another regressiontest for the installer crash; maybe reverting the outcome of that regressiontest might help. Steps to reproduce: wget https://github.com/PowerShell/PowerShell/releases/download/v6.1.6/PowerShell... && wine msiexec /i ./PowerShell-6.1.6-win-x64.msi Then tick "Launch Powershell" in last window, or start it by "wine start pwsh.exe" I attach screenshot of output I got in git where HEAD was 3533605293e8083dae19c5fbd41e2077faf5adc6 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49508 --- Comment #1 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Somehow regression test turned into failure again, pointing to commit that, when reverted, didn`t make the crash go away... Only thing for sure I know now is that it ran fine in wine-5.11 (Staging) If anyone could give pointer how to proceed please do so. Below +relay, it looks like it chokes in RtlGetVersion but that piece of code hasn`t been touched in years so why would it cause a regression..... 0024:Call ntdll.NtQueryInformationProcess(ffffffff,0000000c,0039ceec,00000004,00000000) ret=7b04beb5 0024:Ret ntdll.NtQueryInformationProcess() retval=00000000 ret=7b04beb5 0024:Call ntdll.NtSetInformationProcess(ffffffff,0000000c,0039cf00,00000004) ret=7b04bedf 0024:Ret ntdll.NtSetInformationProcess() retval=00000000 ret=7b04bedf 0024:Ret KERNEL32.SetErrorMode() retval=00008001 ret=00b8d57c 0024:Call KERNEL32.HeapFree(00110000,00000000,0099f3b0) ret=00baef19 0024:Ret KERNEL32.HeapFree() retval=00000001 ret=00baef19 0024:Call ucrtbase.wcscpy_s(051c2eb0,0000000a,0039d078 L"ntdll.dll") ret=00b6ab22 0024:Ret ucrtbase.wcscpy_s() retval=00000000 ret=00b6ab22 0024:Call KERNEL32.GetProcAddress(056c0000,04633363 "RtlGetVersion") ret=00be48c6 0024:Ret KERNEL32.GetProcAddress() retval=056c66ec ret=00be48c6 0024:Call KERNEL32.FlushInstructionCache(ffffffff,05178354,0000000c) ret=00b2f0c8 0024:Call ntdll.NtFlushInstructionCache(ffffffff,05178354,0000000c) ret=7b04b153 0024:Ret ntdll.NtFlushInstructionCache() retval=00000000 ret=7b04b153 0024:Ret KERNEL32.FlushInstructionCache() retval=00000001 ret=00b2f0c8 0024:Call ntdll.RtlGetVersion(0039da90) ret=05178719 0024:trace:seh:KiUserExceptionDispatcher code=c0000005 flags=0 addr=05723F3F ip=05723f3f tid=0024 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49508 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |julliard(a)winehq.org Regression SHA1| |8a169390c9ef4d8a43b604558c4 | |194a052473c0c --- Comment #2 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Hi, did regressiontest: 8a169390c9ef4d8a43b604558c4194a052473c0c is the first bad commit commit 8a169390c9ef4d8a43b604558c4194a052473c0c Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Jun 30 12:01:37 2020 +0200 ntdll: Build with msvcrt. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> So same commit is in bug https://bugs.winehq.org/show_bug.cgi?id=49529, maybe related or dupe? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49508 --- Comment #3 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Additional note: reverting the "-no-cygwin" in Makefile.in makes the crash dissapear in wine-5.12, (you need revert also parts of next two commits to get it compiled again though) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49508 --- Comment #4 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Still present in current git; Apart from regression test also found that compiling with --without-mingw makes the crash dissapear. So what to do more to get some attention to this bug....................... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49508 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Powershell 6.* (pwsh.exe) |Powershell 6.* (pwsh.exe) |crashes at start |crashes with "abnormal |(regression) |program termination" --- Comment #5 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- It looks like this is partly fixed by https://www.winehq.org/pipermail/wine-cvs/2020-July/146782.html and https://www.winehq.org/pipermail/wine-cvs/2020-July/146783.html When I run something like "wine pwsh.exe -c ls" it doesn`t crash anymore and works fine, but when I do "wine pwsh.exe" it exits out with "abnormal termination" or something the like. Building wine with --without-mingw still makes the error go away, and program works fine as expected. I adjust title accordingly -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49508 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- duplicate, see bug 49698 for fixing patches *** This bug has been marked as a duplicate of bug 49698 *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49508 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Duplicate. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla