From: Paul Smith <psmith@gnu.org>
To: gdb@sourceware.org
Subject: Tools to classify / uniquify core dumps or stack traces?
Date: Thu, 01 Aug 2013 19:26:00 -0000 [thread overview]
Message-ID: <1375385181.3028.5.camel@homebase> (raw)
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?
next reply other threads:[~2013-08-01 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 19:26 Paul Smith [this message]
2013-08-01 19:36 ` Jan Kratochvil
2013-08-01 23:05 ` Aurelian Melinte
2013-08-02 1:13 ` Paul Smith
2013-08-02 8:59 ` Phil Muldoon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1375385181.3028.5.camel@homebase \
--to=psmith@gnu.org \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox