From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23813 invoked by alias); 28 Jul 2009 06:44:42 -0000 Received: (qmail 23791 invoked by uid 22791); 28 Jul 2009 06:44:41 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-ew0-f217.google.com (HELO mail-ew0-f217.google.com) (209.85.219.217) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 28 Jul 2009 06:44:33 +0000 Received: by ewy17 with SMTP id 17so3581782ewy.24 for ; Mon, 27 Jul 2009 23:44:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.7.67 with SMTP id 45mr1921698weo.95.1248763470944; Mon, 27 Jul 2009 23:44:30 -0700 (PDT) Date: Tue, 28 Jul 2009 06:44:00 -0000 Message-ID: Subject: Trying to spot memory corruption with core dump From: Pavel Shevaev To: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 2009-07/txt/msg00216.txt.bz2 Folks, could you please share any tips on spotting possible memory corruption by examining the core dump? My application seg. faults every several hours under moderate load and the core dump points to malloc/calloc which I believe is a sign I have a serious memory corruption somewhere in my application. The problem is the fact I can not trace the problematic place in the code and I wonder if the core dump can give me some more clues. Somebody told me I could examine +-200 bytes of the memory where the last exception happened but I don't really understand what I can find there. For me it's just the raw amount of bytes... Thanks in advance. -- Best regards, Pavel