This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Trying to spot memory corruption with core dump

From: Pavel Shevaev <pacha dot shevaev at gmail dot com>
To: Paul Pluzhnikov <ppluzhnikov at google dot com>
Cc: gdb at sourceware dot org
Date: Tue, 28 Jul 2009 11:11:48 +0400
Subject: Re: Trying to spot memory corruption with core dump
References: <d9c3f61a0907272344q697efd1ag1d9b073be4df94b0@mail.gmail.com> <8ac60eac0907272358n7cd27407va0a9982ea4d466bc@mail.gmail.com>

> 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

Follow-Ups:
- Re: Trying to spot memory corruption with core dump
  - From: Paul Pluzhnikov

References:
- Trying to spot memory corruption with core dump
  - From: Pavel Shevaev
- Re: Trying to spot memory corruption with core dump
  - From: Paul Pluzhnikov

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]