Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs Date: Wed, 10 Dec 2003 15:16:43 -0600 (CST) From: Brian Ford X-X-Sender: ford@eos To: Michael Robbert cc: cygwin@cygwin.com Subject: Re: Setup hangs in postinstall In-Reply-To: <3FD78817.9020806@mines.edu> Message-ID: References: <3FD617A6.8050806@mines.edu> <3FD6222D.6040702@m4x.org> <3FD77B62.90909@mines.edu> <3FD78817.9020806@mines.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 10 Dec 2003, Michael Robbert wrote: > Brian Ford wrote: > > On Wed, 10 Dec 2003, Michael Robbert wrote: > >>Everybody, > >>Some new information I got today. I found another user on our campus > >>that is having the problem on two different machines, but not a third. > >>All of them running Windows XP. So far every machine I have seen it on > >>is running XP and is a recent new install of Cygwin. Does anybody think > >>that they could get closer to a solution if I were to provide you with a > >>machine to play with remotely where the problem happens every time? > >> > > Why not try to debug it your self? > > > Gladly, I just need to know what to do. I'm not a developer, just a > lowly SysAdmin so I may need some hand holding. > > > Have you tried to strace it? > > > Yes, I think that this was included in my initial Email. strace produces > no output. > Sorry, I remember now. > I have tried attaching to a running/hung one as well as running: > By that you mean "strace -p pid_of_hung_process"? IIRC, "strace -p pid" is broken in the current release. You need a newer one to do that. > strace sh -c TEST=`uname -s` > Both produced nothing, I suspect that the hang is actually happening > outside of the sh that I create in the latter. > What do you mean by outside of? That command should produce some output regardless, even if it is just Cygwin startup stuff *way* before it gets to the backtick evaluation. > > Can you get a stack trace of the hang in gdb? Note: You may need a debug > > version of the cygwin1.dll or shell for this to be valid. I will provide > > the former if you are willing to test it. > > > Please provide along with instructions of what to do. > Ok, but first have you tried "gdb /bin/sh.exe sh_pid" to get a stack trace? If you can't do that, it won't much matter. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- 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/