X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 4 Mar 2013 15:25:01 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: segfault in recent snapshots Message-ID: <20130304142501.GG2481@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20130302202911.GA1371@ednor.casa.cgf.cx> <20130303180626.GA5313@ednor.casa.cgf.cx> <20130304131735.GF2481@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mar 4 13:21, Henry S. Thompson wrote: > Corinna Vinschen writes: > > > Since you're running GDB anyway, what does `bt' print when the SEGV > > occured? > > #0 0x003d0000 in ?? () > #1 0x610fcf7c in pthread::init_mainthread () > at > /netrel/src/cygwin-snapshot-20130301-1/winsup/cygwin/thread.cc:336 This piece of code hasn't changed since 2011. The jump to 0x003d0000 looks pretty bad, and it's very lielly not a problem in the Cygwin DLL, given that this code is called for every single non-forked process. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer 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