X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Tue, 7 Feb 2012 17:45:48 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin > 1.7.9: Segmentation faults / STATUS_STACK_OVERFLOW
Message-ID: <20120207164548.GD3178@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <0C11C5BF0B29FD43A8D0250F711D497F89E1DD585C AT ex01-ubitronix DOT ubitronix DOT local>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <0C11C5BF0B29FD43A8D0250F711D497F89E1DD585C@ex01-ubitronix.ubitronix.local>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Note-from-DJ: This may be spam

On Feb  7 17:31, Manuel Wienand wrote:
> Hi,
> 
> I have the problem that I get a segmentation fault on the newer versions of the cygwin1.dll when debugging and a STATUS_STACK_OVERFLOW exception when running without debugger.
> I did an update of my cygwin stuff on Monday, and I'm using the latest snapshot dll. I'm quite sure it has something to do with the dll, because I did clean and rebuild with newest
> cygwin versions. Since this wasn't working, I got my old dll (from 29.03.2011) and it worked again.  I tried some other snapshot versions (up to 04.06.2011, since there are no old ones),
> but none of them worked.
> 
> If I can get older snapshot versions, I might be able to track it down. But then again stack problems are hard to catch.
> I compiled my code with -fstack-protector-all --param ssp-buffer-size=4, but this didn't help me so far (well, maybe I'm not using it right.).
> 
> Stacktrace of the first segmentation fault:
> Thread [11] 0 (Suspended : Signal : SIGSEGV:Segmentation fault)          
> _alloca() at ../../../libgcc/../gcc/config/i386/cygwin.asm:45 0x6116fd02	
> __small_vswprintf() at /netrel/src/cygwin-snapshot-20120202-1/winsup/cygwin/smallprint.cc:369 0x610dbdfe	
> 0x0	

Can you please create a simple testcase, in plain C, which allows to
reproduce the problem with minimal code?


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple