From: Michael S. Z. <ms...@mo...> - 2005-06-04 21:00:57
|
On Sat June 4 2005 14:18, Michael S. Zick wrote: > On Sat June 4 2005 13:08, Michael S. Zick wrote: > > An update of results to date; Hugh, I have driven my system with msys-1.10 and bash-2.04 far beyond anything encountered in a 'configure' script. Yes, I can get that combination to show problems, but I do not think they are what you are seeing. What can I say? 1) Make sure you do not have a broken sed(.exe) get the newest one you can find - there is a note somewhere on this subject. 2) Once inside the msys bash command shell... echo $PATH examine and set to the simplest possible path. watch out for having directory paths to software that might have been built with msys/cygwin. Then set that simplest possible path by: export PATH='/what/ever:/c/I decided:/to/use' Try to avoid any paths with spaces in them; if that is not possible, use the dos 8.3 format for those names. Group, What did I find? (I changed my rxtest to include PIDs in the messages.) Probably the most interesting set is: hello 0 PID: 10232 0 [main] sh 5988 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump 0 [main] sh 8080 sync_with_child: child 2288(0x6D0) died before initialization with status code 0x80 160 [main] sh 8080 sync_with_child: *** child state waiting for longjmp ./rxtest: fork: Resource temporarily unavailable hello 0 PID: 6504 0 [main] sh 5616 sync_with_child: child 2088(0x6D0) died before initialization with status code 0x80 129 [main] sh 5616 sync_with_child: *** child state waiting for longjmp ./rxtest: fork: Resource temporarily unavailable ./rxtest: fork: Permission denied Those errors are not recoverable - they should not be returning EAGAIN The test run did eventually crater and zombie a half dozen copies of sh.exe but the system did (after 5 minutes) clean up the mess. On its way to eventually death, there where other errors reported. I have attached the output of the full test run. Mike |