From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19467 invoked by alias); 28 Jul 2009 17:32:01 -0000 Received: (qmail 19455 invoked by uid 22791); 28 Jul 2009 17:32:00 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_05 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 28 Jul 2009 17:31:54 +0000 Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.67.167]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 66AD43C00A; Tue, 28 Jul 2009 10:31:50 -0700 (PDT) Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) by mailhost2.vmware.com (Postfix) with ESMTP id 470338EAD1; Tue, 28 Jul 2009 10:31:50 -0700 (PDT) Message-ID: <4A6F3450.403@vmware.com> Date: Tue, 28 Jul 2009 17:32:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: Pavel Shevaev CC: Paul Pluzhnikov , "gdb@sourceware.org" Subject: Re: Trying to spot memory corruption with core dump References: <8ac60eac0907272358n7cd27407va0a9982ea4d466bc@mail.gmail.com> <8ac60eac0907280642h4700d7d5m95204a6e201281da@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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/msg00222.txt.bz2 Pavel Shevaev wrote: > P.S. thanks again for being helpful, I've been trying to spot this > memory corruption for a week, I think I'm gradually going mad, so, > _any_ help is highly appreciated Don't worry, this is a typical symptom of trying to analyze heap corruption problems. ;-)