ry I can't be any more helpful right now (although I'm willing
to spend some time debugging it). Any insight would be appreciated.
I attached my 'cygcheck -srv' dump.
Thanks,
Antoine Labour
-Original Message-
From: Geoffrey Ruscoe [mailto:[EMAIL PROTECTED]
Sent: Thursday, No
Nicholas Wourms wrote:
news.gmane.org wrote:
I'm running in concurrences 5 complex bash batch, and sometimes (2
times on
3) one or more (very rarely) batch stop to do something. I've put a
lot of
trace to see where is the problem, but seems rarely arrived at the
same line
of code.
I've also tr
Brian Ford wrote:
On Tue, 2 Dec 2003, Christopher Faylor wrote:
On Tue, Dec 02, 2003 at 10:42:38AM -0600, Brian Ford wrote:
Could you try a snapshot that includes it?
FWIW, I ran the test case overnight on my old 450 MHz Pentium Pro SGI 320
running NT4, all packages up-to-date, and a cvs compiled
Michael Robbert wrote:
Brian,
Thanks for your quick response, but we have done multiple searches on
google and the list archives. I read every post that I could find about
the problems in October where setup was hanging during postinstall. That
is where I got many of my ideas for debugging alrea
Michael Robbert wrote:
I'm sorry, I don't have a copy of XP to try this with, but it would
appear to be a bug in uname (since it gives no output from the
commandline)
Does it uname hang or just return empty? Is there any error codes? Try:
/bin/uname -a ; echo $?
Also, could you *attach* (unco
Brian Ford wrote:
Why not try to debug it your self?
Have you tried to strace it?
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.
FWIW here's a link to a p
Brian Ford wrote:
Antonine, you might try the same. It might be more informative to see
how we got there than to see just a static stack dump.
strace -o /tmp/tracelog.txt /bin/bash.exe -c yourtestcase.sh.
Then send the tail of that log when you get it to happen.
Unfortunately, it doesn't seem to
Igor Pechtchanski wrote:
Cygwin setup will sometimes defer replacing in-use files until the next
reboot. If setup asked you to reboot after upgrading Cygwin last time,
that means it had some files scheduled for replacement, while you were
still running with the old versions of the DLLs. Rebootin
8 matches
Mail list logo
