On Thu, 30 Nov 2017 09:50:57, David Macek wrote: > On 30. 11. 2017 1:44, Houder wrote: > > ntoskrnl.exe!memset+0x61a > > ntoskrnl.exe!KeWaitForMultipleObjects+0xd52 > > ntoskrnl.exe!KeWaitForSingleObject+0x19f > > ntoskrnl.exe!PoStartNextPowerIrp+0xbd0 <=3D=3D=3D=3D ????? > > ntoskrnl.exe!PoStartNextPowerIrp+0x186d <=3D=3D=3D=3D ????? > > cygwin1.dll!reent_data+0x5f0 > > cygwin1.dll!acl_get_perm+0x9aa1 > > cygwin1.dll!_getreent+0x1097 > > sort.exe+0x5319 > > sort.exe+0x103e0 > > cygwin1.dll!cygwin_dll_init+0x11c2 > > cygwin1.dll!setprogname+0x35c3 > > cygwin1.dll!setprogname+0x3674 > > In my experience, stack traces of Cygwin from MS tools are not very reliab > le. Can you try GDB as well? > > David Macek
Yes, that might very well be the case (I am not familiar with P.E.). That is why I was reluctant to report it. (grasping at straws) Henri -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
