On 09/28/2010 05:09 PM, Eric Blake wrote:
On 09/27/2010 09:43 AM, Ralf Corsepius wrote:
Excluding tests 199 and 205, I finally managed to get a testsuite.log.
[From what I experience, 199 hangs ca. 3 out of 4 times, 205 always
hangs]
Ralf
# -*- compilation -*-
15. tools.at:504: testing autoconf: input from stdin ...
./tools.at:510: echo 'AC_INIT(X, 1.0, bug-autoconf@gnu.org)' |
autoconf -t AC_INIT -
--- /dev/null 2010-09-27 12:19:01.000000000 +0200
+++
/home/admin/tmp/autoconf-2.68/tests/testsuite.dir/at-groups/15/stderr
2010-09-27 12:18:59.419875000 +0200
@@ -0,0 +1,5 @@
+/home/admin/tmp/autoconf-2.68/bin/autoconf: line 82: 2744 Aborted
( test "X`printf %s $as_echo`" = "X$as_echo" ) 2> /dev/null
Something is wrong with your cygwin environment. Simple shell
commands should not be aborting like that. I'm suspecting that you
are running into a case where cygwin's fork() is failing to remap
dependent .dlls to the same address in the child as they were in the
parent. Do you need to rebase your cygwin .dlls, using the
'rebaseall' program?
As I told you before, I am more or less a newbie to cygwin and don't
even understand this remark of yours.
Are you running with an interfering virus checker or other
ill-behaved system-level code-injection application that interferes
with cygwin operation?
You may be better off asking on the cygwin list for ideas how to
diagnose and repair your installation.
http://cygwin.com/faq/faq.using.html#faq.using.bloda
This system doesn't have any of the programs listed on this page installed.
Other than the known failures of 199 and 205 (because of the known
cygwin bugs in named fifo handling), the remaining tests all pass for
me under cygwin 1.7.7.
As I also told you before, all of these errors (except of 199 and 205)
appear at random, sometimes they appear, sometimes they don't.
However, when using autoconf to build real code, I am occasionally
observing sh (== bash) breaksdowns (in unix terms: segfaults)
Ralf
