Message-Id: <200402190552.i1J5qM0e001554@delorie.com> 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 Resent-Message-ID: <20040219055159 DOT 6988 DOT qmail AT sources DOT redhat DOT com> From: "Cliff Geschke" To: Subject: RE: Repeatable crash with CVS version of cygwin1 DLL Date: Wed, 18 Feb 2004 23:03:21 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20040218224324.GA4792@redhat.com> X-Sender: cliff_pa AT geschkefamily DOT com Resent-From: root AT sourceware DOT org Resent-Date: Thu, 19 Feb 2004 05:51:58 +0000 Resent-To: cygwin AT cygwin DOT com I have tried the latest update from CVS. Still crashes, but stackptr does not go out-of-bounds. At some point, _sigbe tries to ret with the top of stack ($esp) value set to 0. Some additional data points: 1. I moved the test .exe file to a Win2000 box running an old cygwin1.dll (file version 1005.5.0.0, product version 1.5.5-cr-0x9b). No crash. The test seems to run fine. 2. I moved the new 1.5.8 cygwin1.dll back to that Win2000 box. Test crashes. It is not feasible for me to put together a simple test program, unless you want load and build RTEMS so you can link to it. If you trust me, I can push you the test .exe file. I can uuencode it to probably get past your filters. But that seems like a poor thing to post to this list. Do you want me to email it or push it somewhere else? Please advise. Cliff Geschke -----Original Message----- From: Christopher Faylor [mailto:cgf-no-personal-reply-please AT cygwin DOT com] Sent: Wednesday, February 18, 2004 4:43 PM Subject: Re: Repeatable crash with CVS version of cygwin1 DLL On Wed, Feb 18, 2004 at 10:31:03AM -0600, Cliff Geschke wrote: >cygwin-1.5.7-1 >cygwin-SPLAT-cygwin-BOP-com Please, avoid putting raw email addresses in messages. They serve no purpose and are spambot fodder. >After doing what you asked, the crash still occurs, but is somewhat >different. Here is what I did. > >1. Loaded cygwin from CVS. I see the relevant routines have all changed. >2. ./configure >3. make >4. build failed for dumper.exe (will send separate email) 5. Replaced >/usr/bin/cygwin1.dll with new-cygwin1.dll 6. Reboot (just to be safe) >7. Ran my test program. > >I am still seeing stackptr being corrupted. I believe it happens after >a setjmp/longjump. See "do_jump" routine below. > >I think the problem is in the "call _set_process_mask" in sigreturn. >That somehow winds up calling _sigbe with the thread stack empty. > >Look for "####" below for start of debug sections. > >I can supply the .exe test program if you wish. > >Good luck and thanks, Thank you for providing an impressive amount of detail. I have made some changes to setjmp/longjmp. I don't know if they fix your problems but I did manage to write a very simple test case which illustrated a problem with using setjmp/longjmp in signal handlers. -- 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/