From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2340 invoked by alias); 22 Apr 2010 09:44:22 -0000 Received: (qmail 2261 invoked by uid 22791); 22 Apr 2010 09:44:21 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Received: from kz-easy.com (HELO almaty.kz-easy.com) (85.214.25.173) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 22 Apr 2010 09:44:07 +0000 Received: from alatau.radix50.net (dslb-088-065-035-251.pools.arcor-ip.net [88.65.35.251]) (authenticated bits=0) by almaty.kz-easy.com (8.13.8/8.13.8/Debian-3) with ESMTP id o3M9i0Wn020898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 22 Apr 2010 11:44:02 +0200 Received: from alatau.radix50.net (localhost [127.0.0.1]) by alatau.radix50.net (8.14.3/8.14.3/Debian-5) with ESMTP id o3M9ht78010499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 22 Apr 2010 11:43:55 +0200 Received: (from ibr@localhost) by alatau.radix50.net (8.14.3/8.14.3/Submit) id o3M9ht8c010498 for gdb@sourceware.org; Thu, 22 Apr 2010 11:43:55 +0200 Date: Thu, 22 Apr 2010 09:44:00 -0000 From: Baurzhan Ismagulov To: gdb@sourceware.org Subject: Re: No useful backtrace in core dump. Message-ID: <20100422094354.GH7781@radix50.net> Mail-Followup-To: gdb@sourceware.org References: <201004220818.o3M8INMG014249@glazunov.sibelius.xs4all.nl> <20100422084947.GA7781@radix50.net> <20100422091645.GD7781@radix50.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-IsSubscribed: yes 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-04/txt/msg00077.txt.bz2 On Thu, Apr 22, 2010 at 05:36:46PM +0800, 代尔欣 wrote: > Hope I do not go wrong direction. This depends on your goal, whether you want to debug this particular case, or you want to solve the backtrace problem in general. If you can reproduce the problem, then running the app under gdb is the easiest way. Otherwise, you could analyze the stack in the core file manually and see callers past abort(). With kind regards, -- Baurzhan Ismagulov http://www.kz-easy.com/