X-Spam-Check-By: sourceware.org Message-ID: <46AC1680.502C59A2@dessent.net> Date: Sat, 28 Jul 2007 21:24:32 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: perl5.8.8 SEGfault and corrupt stack References: <46AA5F93 DOT 4060404 AT tlinx DOT org> <46AB1AFF DOT 40304 AT x-ray DOT at> <46AC0728 DOT 5000009 AT tlinx DOT org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Linda Walsh wrote: > > gdb perl > GNU gdb 6.3.50_2004-12-28-cvs (cygwin-special) > This GDB was configured as "i686-pc-cygwin"...Minimal symbols from perl.exe... > (no debugging symbols found) > (gdb) run -e'print 1' > Starting program: /usr/bin/perl.exe -e'print 1' > Program received signal SIGSEGV, Segmentation fault. > 0x610b48b6 in pthread_key_create () from /usr/bin/cygwin1.dll > (gdb) You're using an outdated version of gdb and you're seeing this phony SIGSEGV because of it. There is no actual segmentation fault here, it's only an artifact of gdb. You can "continue" past it, or better, use an up-to-date version that doesn't suffer from this. This has nothing whatsoever to do with perl at all, you can trigger it with a hello-world program too. Brian -- 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/