X-Spam-Check-By: sourceware.org Date: Wed, 1 Aug 2007 19:38:00 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Stack traces in own program in cygwin Message-ID: <20070801233800.GA9104@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <46B07604 DOT 9000605 AT odd-e DOT com> <46B0ABD2 DOT E4F926E9 AT dessent DOT net> <46B10CFE DOT 1040708 AT odd-e DOT com> <46B117E8 DOT 95E4D9E9 AT dessent DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46B117E8.95E4D9E9@dessent.net> User-Agent: Mutt/1.5.15 (2007-04-06) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Wed, Aug 01, 2007 at 04:31:52PM -0700, Brian Dessent wrote: >Bas Vodde wrote: >>Thanks for the reply. Where can I find the cygwin code that unwinds >>the stack? I might have a look at it anyway :) > >Look at class stack_info in winsup/cygwin/exceptions.cc. It's pretty >simplistic, and I'm pretty sure it will be rendered totally ineffective >by -fomit-frame-pointer. Yep. It will. That's the reason why we use -fomit-frame-pointer sparingly when building cygwin. cgf -- 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/