From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20212 invoked by alias); 28 Jul 2009 07:12:01 -0000 Received: (qmail 20194 invoked by uid 22791); 28 Jul 2009 07:11:58 -0000 X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=BAYES_00,J_CHICKENPOX_35,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from ey-out-1920.google.com (HELO ey-out-1920.google.com) (74.125.78.148) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 28 Jul 2009 07:11:51 +0000 Received: by ey-out-1920.google.com with SMTP id 5so888735eyb.24 for ; Tue, 28 Jul 2009 00:11:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.47.71 with SMTP id s49mr1968853web.129.1248765108732; Tue, 28 Jul 2009 00:11:48 -0700 (PDT) In-Reply-To: <8ac60eac0907272358n7cd27407va0a9982ea4d466bc@mail.gmail.com> References: <8ac60eac0907272358n7cd27407va0a9982ea4d466bc@mail.gmail.com> Date: Tue, 28 Jul 2009 07:12:00 -0000 Message-ID: Subject: Re: Trying to spot memory corruption with core dump From: Pavel Shevaev To: Paul Pluzhnikov Cc: 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/msg00218.txt.bz2 > On Linux/ix86 and x86_64, nothing beats Valgrind (for finding heap corruption). Oh, forgot to mention this on the very first post. I'm using linux x86_64 and I'm aware of Valgrind and I even tried it....the problem is it doesn't detect any memory corruption at all and what's even more amazing my application doesn't seg.fault under Valgrind even after running the whole day :( I think it's because Valgrind slows down the application considerably and some how the rare edge case when memory corruption occurs simply doesn't happen. -- Best regards, Pavel