From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32649 invoked by alias); 5 Feb 2010 17:36:14 -0000 Received: (qmail 32639 invoked by uid 22791); 5 Feb 2010 17:36:13 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 05 Feb 2010 17:36:09 +0000 Received: from int-mx04.intmail.prod.int.phx2.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.17]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o15Ha4lL024541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 5 Feb 2010 12:36:04 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx04.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o15Ha3md009605; Fri, 5 Feb 2010 12:36:03 -0500 Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id o15Ha24A012406; Fri, 5 Feb 2010 12:36:03 -0500 Received: by opsy.redhat.com (Postfix, from userid 500) id 1756A378111; Fri, 5 Feb 2010 10:36:02 -0700 (MST) From: Tom Tromey To: Cristian Zamfir Cc: gdb@sourceware.org Subject: Re: backtrace when corrupt stack References: <33F51508-83E5-4791-ADA3-DA8591582C49@epfl.ch> Reply-To: tromey@redhat.com Date: Fri, 05 Feb 2010 17:36:00 -0000 In-Reply-To: <33F51508-83E5-4791-ADA3-DA8591582C49@epfl.ch> (Cristian Zamfir's message of "Fri, 5 Feb 2010 16:24:11 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-02/txt/msg00033.txt.bz2 >>>>> "Cristian" == Cristian Zamfir writes: Cristian> Is it possible to get an accurate backtrace in this case? In addition to what Robert said, you may want to try valgrind instead of gdb in a case like this. That is usually the tool I try first when I have this kind of bug. Tom