From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29888 invoked by alias); 9 Jan 2006 09:33:08 -0000 Received: (qmail 29877 invoked by uid 22791); 9 Jan 2006 09:33:08 -0000 X-Spam-Check-By: sourceware.org Received: from cumulus.netspace.net.au (HELO mail.netspace.net.au) (203.10.110.72) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 09 Jan 2006 09:33:06 +0000 Received: from [192.168.0.10] (220-253-60-77.VIC.netspace.net.au [220.253.60.77]) by mail.netspace.net.au (Postfix) with ESMTP id F0B787BDFC for ; Mon, 9 Jan 2006 20:33:01 +1100 (EST) Message-ID: <43C22DD0.5080503@netspace.net.au> Date: Mon, 09 Jan 2006 09:33:00 -0000 From: Russell Shaw User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.11) Gecko/20050914 Debian/1.7.11-1 MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Core dumps Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00065.txt.bz2 Hi, When i make my code core-dump using abort(), and read the core with "target core core", the back-trace shows a corrupted stack. How do i make a core dump that has an intact stack i can trace thru? Should i use something other than abort()?