Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Mon, 8 Mar 2004 18:53:16 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Rolf Campbell cc: cygwin AT cygwin DOT com Subject: Re: Snapshot 20040306: make hangs In-Reply-To: Message-ID: References: <40451E42 DOT 4070806 AT scytek DOT de> <4044B845 DOT 7000003 AT scytek DOT de> <20040303033617 DOT GA5325 AT redhat DOT com> <20040304021428 DOT GA5815 AT redhat DOT com> <20040304155948 DOT GA21030 AT redhat DOT com> <20040305193352 DOT GA4324 AT redhat DOT com> <20040305193801 DOT GA4500 AT redhat DOT com> <20040305224218 DOT GA9347 AT redhat DOT com> <20040308165246 DOT GA27926 AT redhat DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Mon, 8 Mar 2004, Rolf Campbell wrote: > Christopher Faylor wrote: > > If you want to analyze the strace yourself and offer comment, then > > please do so. Sending strace snippets is normally useless. 99% of the > > time, people send the equivalent of a photo of an accident scene with > > the thought that the picture will show why the accident occurred, i.e., > > the strace snippet is worthless. I gave up trying to inspect > > unsolicited strace output a long time ago. > > cgf > > I did notice one pattern after stairing blindly at strace output for a > while. Every time it freezes, there is a: > > 43 4628798 [sig] make 2064 setup_handler: signal 20 not delivered > 47 4628845 [sig] make 2064 sigpacket::process: returning 0 > > very near the end of strace output (last 10 lines). And on every > successful run that I've looked at, I see: > > 43 6057447 [sig] make 3768 setup_handler: signal 20 delivered > 41 6057488 [sig] make 3768 sigpacket::process: returning 1 > > in the last 150 lines of stace output. > > What is signal 20 anyway? > > I see it get 'not delivered' in the success runs too, but never so close > to the end (1000's of lines up from the end). > > -Rolf $ kill -l 1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL 5) SIGTRAP 6) SIGABRT 7) SIGEMT 8) SIGFPE 9) SIGKILL 10) SIGBUS 11) SIGSEGV 12) SIGSYS 13) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGURG 17) SIGSTOP 18) SIGTSTP 19) SIGCONT 20) SIGCHLD 21) SIGTTIN 22) SIGTTOU 23) SIGIO 24) SIGXCPU 25) SIGXFSZ 26) SIGVTALRM 27) SIGPROF 28) SIGWINCH 29) SIGLOST 30) SIGUSR1 31) SIGUSR2 Also, there's some discussion on cygwin-patches that might be helpful. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/