Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: From: "Trevor Forbes" To: Subject: RE: Please try the latest snapshot -- it is close to cygwin 1.5.6 Date: Thu, 25 Dec 2003 16:05:24 +0930 Message-ID: <005d01c3cab1$47cc2850$6500a8c0@ufo> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20031225043349.GB12748@redhat.com> X-IsSubscribed: yes I was running the open_posix_testsuite against the current "homebuilt" cygwin1.dll but I get the same error if I use the new dll to build itself. It only happens randomly to gcc.exe but it always errors at the same location "0x61085fba". I run the testsuite when I built the dll which gives: FAIL: msgtest.c (execute) FAIL: semtest.c (execute) FAIL: shmtest.c (execute) FAIL: pthread/mainthreadexits.c (execute) === winsup Summary === # of expected passes 259 # of unexpected failures 4 # of expected failures 14 The pthread test is the only abnormal failure as I am not using the cygserver. I looked at the mainthreadexits.c test and I was not sure if the test was correct. So that's what lead me to try out the open_posix_testsuite. I am currently "Googling" for different debugging methods and contemplating having a Xmas drink or two. I tried the "how-to-debug-cygwin.txt" but GDB did not provide any useful information. Sorry I am not more helpful. Merry Xmas to all. Trevor -- 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/