From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22037 invoked by alias); 2 Aug 2013 08:59:20 -0000 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 Received: (qmail 22024 invoked by uid 89); 2 Aug 2013 08:59:19 -0000 X-Spam-SWARE-Status: No, score=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RDNS_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 Received: from Unknown (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 02 Aug 2013 08:59:19 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r728x9tN023924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Aug 2013 04:59:09 -0400 Received: from localhost.localdomain (ovpn-112-38.ams2.redhat.com [10.36.112.38]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r728x7lO021787; Fri, 2 Aug 2013 04:59:07 -0400 Message-ID: <51FB74DA.400@redhat.com> Date: Fri, 02 Aug 2013 08:59:00 -0000 From: Phil Muldoon MIME-Version: 1.0 To: psmith@gnu.org CC: Jan Kratochvil , gdb@sourceware.org Subject: Re: Tools to classify / uniquify core dumps or stack traces? References: <1375385181.3028.5.camel@homebase> <20130801193547.GA12116@host2.jankratochvil.net> <1375406012.3028.38.camel@homebase> In-Reply-To: <1375406012.3028.38.camel@homebase> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-08/txt/msg00004.txt.bz2 On 02/08/13 02:13, Paul Smith wrote: > On Thu, 2013-08-01 at 21:35 +0200, Jan Kratochvil wrote: >> On Thu, 01 Aug 2013 21:26:21 +0200, Paul Smith wrote: >>> Hi all. I've got an environment where I'm getting lots of core dumps >>> from various places and it's very tedious to go through them and >>> determine which ones are for unique problems, and which are essentially >>> duplicates (same bug causing the core dump). >>> >>> I was thinking of throwing together some kind of Perl or Python script >>> that could compare and categorize stack traces, but I thought surely >>> someone must have done something like this before. >>> >>> Anyone have any pointers or thoughts about something like this? >> >> ABRT, it has several backends how to report the results (the typical one is >> Bugzilla), it also supports heuristic duplicates detection etc. >> It is shipped in all recent Fedora releases by default and it is also >> a project deployable on any OS: >> https://fedorahosted.org/abrt/ >> >> There is also Apport (I do not have experience with it). > > It looks like btparser is close to what I need. It's an unusual choice, > IMHO, to use C to implement something which so fundamentally depends on > text manipulation; I would have chosen Perl or Python myself. But I'll > definitely take a look. Why not use the Python API in GDB to automate your task? http://sourceware.org/gdb/current/onlinedocs/gdb/Python.html#Python If there are things missing in the API regarding what you need for your task, I will be happy to add them. Cheers, Phil