X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sun, 5 Jul 2009 13:44:34 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Segmentation fault when exception is thrown or assertion fails [g++/gcc] Message-ID: <20090705174434.GF21218@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4A50A18B DOT 6070407 AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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 Sun, Jul 05, 2009 at 05:21:50PM +0100, Roman Werpachowski wrote: >On Sun, Jul 5, 2009 at 1:50 PM, Dave Korn wrote: >> ?Well, what happened was that there's a bug somewhere, and while cygwin was >> in the process of dumping the stack trace for the abort caused by your >> assertion firing, > >One more question: how can I use this stack trace to debug genuine >errors? "gdb -c" cannot load it. The stack dump is for human consumption. gdb doesn't know anything about it. You can look up the addresses in gdb by doing something like: (gdb) l *0xf00f00fa Or you can use addr2line. If you want a real core dump see: http://www.cygwin.com/cygwin-ug-net/using-utils.html#dumper cgf -- 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