From: BGINFO f. X <bgi...@kz...> - 2014-01-02 16:26:29
|
Hello, I have created the bug in http://sourceforge.net/p/mingw/bugs/2154/ I hope you can help me. Thanks al lot. Regards. 2013/12/29 BGINFO for X <bgi...@kz...> > Hello to all, I think that I have found a bug on MSYS. > > This issue happens ONLY when launching ANY MSYS binary as a > "NTAUTORITY\SYSTEM" user. > > It happens with : ls.exe, sh.exe, env.exe .... > > To test it, open a cmd.exe as: "psexec -i -s -d cmd.exe". Then, execute > any msys binary, and the process takes at least 24 SECONDS to be opened. > > Monitoring the process with process monitor shows the problem. See the > attached image. It seems the the problem is in the last cscapi.dll call > and before the samcli.dll call. > > Creating also a process dump with procdump (sysinternals utility) you can > get an EXCEPTION(0xc0000008). > > > ################################################################################## > "In sh_131229_121226.dmp the assembly instruction at 0x776012c7 which > does not correspond to any known native module in the process > has caused an unknown exception (0xc0000008) on thread 0. > > Type of Analysis Performed Combined Crash/Hang Analysis > Machine Name K-PC > Operating System Windows 7Service Pack 1 > Number Of Processors 2 > Process ID 3536 > Process Image C:\MinGWdevelopment\msys\1.0\bin\sh.exe > System Up-Time 00:00:00 > Process Up-Time 00:00:00 > Processor Type X86 > Process Bitness 32-Bit > > Top 5 Threads by CPU time > Note - Times include both user mode and kernel mode for each thread > Thread ID: 0 Total CPU Time: 00:00:00.015 Entry Point for Thread: > sh+1000 > Thread ID: 1 Total CPU Time: 00:00:00.000 Entry Point for Thread: > msys_1_0!getpass+3750 > > Thread report > > Thread 0 - System ID 3120 > > Entry point sh+1000 > Create time 29/12/2013 12:12:26 > Time spent in user mode 0 Days 00:00:00.000 > Time spent in kernel mode 0 Days 00:00:00.015 > > This thread is not fully resolved and may or may not be a problem. Further > analysis of these threads may be required. > > Function > > ntdll!ZwClose+12 > kernel32!BaseRegCloseKeyInternal+41 > kernel32!RegCloseKey+7d > msys_1_0!regsub+5fa > msys_1_0!getpass+3ef8 > msys_1_0!select+5319 > msys_1_0!_assert+3035 > msys_1_0!dll_crt0+125 > sh+6f62f > sh+103e > kernel32!BaseThreadInitThunk+e > ntdll!__RtlUserThreadStart+70 > ntdll!_RtlUserThreadStart+1b > > > Thread 1 - System ID 3464 > > Entry point msys_1_0!getpass+3750 > Create time 29/12/2013 12:12:26 > Time spent in user mode 0 Days 00:00:00.000 > Time spent in kernel mode 0 Days 00:00:00.000 > > Function > > ntdll!RtlUserThreadStart > > ##################################################################################3 > > > Sorry for my ignorance, but I'm not a programmer. > > Could you help me? > > I use msys 1.0.18 and I tested and verified the problem with: W7 and > W2008 R2. > > Thanks a lot. > > |