On Mon, Jun 25, 2012 at 05:00:57PM +0200, marco atzeri wrote: >On 6/25/2012 4:45 PM, Christopher Faylor wrote: >> On Mon, Jun 25, 2012 at 01:57:26PM +0200, marco atzeri wrote: >>> On 6/25/2012 11:36 AM, marco atzeri wrote: >>>> On 6/25/2012 11:00 AM, Corinna Vinschen wrote: >>>>> On Jun 25 10:37, marco atzeri wrote: >>>>>> >>>>>> A normal exception should kill just the running process, while >>>>>> I see that xprobe_comp, bash, mintty are killed and >>>>>> also others bash and mintty processes are taking down. >>>>> >>>>> Really all processes or just all processes in the same terminal window? >>>> >>>> all processes in all the available terminal windows. >>>> 3 mintty and 3 bash are taken down and they were indepedently >>>> created by the start menu >>>> >>>>> >>>>> Corinna >>>>> >>>> >>>> I will check if today cgf's changeset make any difference >>>> >>>> Regards >>>> Marco >>>> >>>> >>> hi Corinna, >>> no difference. It takes down everything >>> >>> but you are right about mintty, it is crashing and the stackdump >>> are located at c:\windows\SySWOW64, I only noticed with procmon. >>> >>> --------------------------------------------------------------------- >>> Exception: STATUS_ACCESS_VIOLATION at eip=610CE726 >>> eax=610CE710 ebx=0000010C ecx=777B0000 edx=0008E3C8 esi=0028A5B8 >>> edi=8005A088 >>> ebp=0028A468 esp=0028A450 program=E:\cygwin\bin\mintty.exe, pid 6652, >>> thread main >>> cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B >>> Stack trace: >>> Frame Function Args >>> 0028A468 610CE726 (8004EF58, 0028A5B8, E65DA9C7, 231FFA3E) >>> 0028A488 610D05CE (0028A5B8, 0028A648, 0028A540, 0028A520) >>> 0028A618 610D146A (00000002, 0028A648, 0028A540, 0028A520) >>> 24479433 [main] mintty 6652 exception::handle: Exception: >>> STATUS_ACCESS_VIOLATION >>> 24495658 [main] mintty 6652 exception::handle: Error while dumping state >>> (probably corrupted stack) >>> ---------------------------------------------------------------------- >>> >>> $ addr2line.exe -e cygwin1.dll 610CE726 >>> /pub/cygwin/cvs/src_new/winsup/cygwin/select.cc:687 >>> >>> $ addr2line.exe -e cygwin1.dll 610D05CE >>> /pub/cygwin/cvs/src_new/winsup/cygwin/select.cc:243 >>> >>> $ addr2line.exe -e cygwin1.dll 610D146A >>> /pub/cygwin/cvs/src_new/winsup/cygwin/select.cc:252 >> >> How long did this take to crash mintty? >> >> cgf >> > > >7 sec on my slow PC. > From procmon I saw that xprobe_comp and the shells it reises continue >to run for a while and only after they close. > >on 20120611 the full successful run is 45 sec.
I let my run on 20120611 go for more than that. The system eventually became unresponsive and I had to power cycle it. Probably I could have rebooted via Start if I'd been more patient, though. I have another vague idea about this problem and will be checking in another change soon. cgf -- 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
