Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <001501c2c7ce$6a0afa90$78d96f83@pomello>
From: "Max Bowsher" <maxb@ukf.net>
To: <cygwin@cygwin.com>
References: <00d001c2c6d3$156b2e20$78d96f83@pomello> <3E3819CD.8060209@hekimian.com> <20030129184248.GD11143@redhat.com>
Subject: Re: rsync hang - strace output - any ideas?
Date: Wed, 29 Jan 2003 19:41:27 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:
> On Wed, Jan 29, 2003 at 01:13:33PM -0500, Joe Buehler wrote:
>> Max Bowsher wrote:
>>
>>> I got this from gdb:
>>> (gdb) bt
>>> #0  0x77f767ce in ?? ()
>>>
>>> i.e. nothing useful. If anyone has any suggestions for getting more
>>> info, please say.
>>
>> I posted a script to this list some time back that can be used to
>> translate NT addresses (like the 0x77f767ce above) to function
>> names.  This can be
>> a help in understanding what a thread is hanging on.
>
> The newly released version of gdb may do this automatically.  I
> accidentally included a patch from the net in this version which
> added this functionality. I meant to remove it because it was rumored
> to have problems but it seems
> to be working ok, AFAICT.

Yes, it's working fine for me. Unless it really messes up, can you leave it
in?

> When doing backtraces, please remember that thread 1 is the main
> thread. Usually that is the thread which is doing something
> interesting.

Yes. I found that out and posted a new backtrace. However, I've just
realized that the so-called hang, was in fact merely a blocking accept()
call that wasn't supposed to block. *embarrased* :-)

And, for various reasons, I don't think it is the same hang bug that others
have been mentioned.


Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/