public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Funny hang with snapshop 20050920
Date: Sat, 24 Sep 2005 01:11:00 -0000	[thread overview]
Message-ID: <20050924001110.GA1390@trixie.casa.cgf.cx> (raw)
In-Reply-To: <43348E75.7080309@scytek.de>

On Fri, Sep 23, 2005 at 07:23:33PM -0400, Volker Quetschke wrote:
>Christopher Faylor wrote:
>>On Thu, Sep 22, 2005 at 10:18:51PM -0400, Volker Quetschke wrote:
>>
>>>My favorite testcase (building OOo) started hanging again.
>>>...
>>>But now the *really* strange part begins: You can break the hang by doing
>>>"ls /proc/3176/fd" !?
>>>and the build continues (until the next hang).
>>>
>>>Sorry, we're unable to create a reduced testcase but we thought the
>>>strange symptoms might help pinpoint the problem.
>>>
>>>Attached you also find the cygcheck output of that system.
>>
>>Does sending a 'kill -CONT 3176' also unstick things?  Both situations 
>>send a
>>signal to the process.
>
>Sorry, this question got lost, but ...
>
>>How about attaching to the hung process with strace?  You didn't mention
>>that.
>
>he tried to attach and strace was standing there without output.
>A "ls /proc/<pid>/fd" produced then the first four lines of the
>attached strace log but tcsh still hung.

You know, I noticed yesterday that there was some information missing
from the strace output in the open_shared function and, of course, I
didn't fix it.  Oh well.  That means that I don't get much from this
strace output.

>Several "ls /proc/<pid>/fd" later it continued and produced the
>rest of that logfile.
>
>Did you notice that the WINPID of the hanging tcsh is the same as
>the PID? This is always the case if it hangs.

That just means that the process has forked but hasn't execed anything.
I don't think that's significant.

>Additional info: Both tcsh processes exist with the respective
>WINPID in taskmgr.

I'd expect that they did or you wouldn't be able to attach to them.

There is a new snapshot up there now.  I think I've given up on the
technique that I was trying to use to fix the Windows 98 bug.  I've
yanked out a lot of the code and simplified things but I hope I haven't
caused the bug to reemerge.

Could you try the 2005-09-23 snapshot?  Same rules.  I'd still like to
know if sending a CONT to the hung process fixes it as well as ls
/proc/nnn/fd and I'd still like to see the strace output if the process
hangs again.

Also could anyone who could duplicate the Windows 98 error popup dialog
confirm or deny if it is still fixed?

cgf

--
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/

  reply	other threads:[~2005-09-24  0:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23  3:09 Volker Quetschke
2005-09-23  6:09 ` Christopher Faylor
2005-09-23  7:08   ` Volker Quetschke
2005-09-24  0:42   ` Volker Quetschke
2005-09-24  1:11     ` Christopher Faylor [this message]
2005-09-26 13:33       ` Eric Blake
2005-09-26 13:35         ` Christopher Faylor
2005-09-27 11:25       ` Aaron Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050924001110.GA1390@trixie.casa.cgf.cx \
    --to=cgf-no-personal-reply-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).