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: Samuel Bronson <naesten at gmail dot com>
To: Pavel Shevaev <pacha dot shevaev at gmail dot com>
Cc: Paul Pluzhnikov <ppluzhnikov at google dot com>, gdb at sourceware dot org
Date: Tue, 28 Jul 2009 17:51:09 -0400
Subject: Re: Trying to spot memory corruption with core dump
References: <d9c3f61a0907272344q697efd1ag1d9b073be4df94b0@mail.gmail.com> <8ac60eac0907272358n7cd27407va0a9982ea4d466bc@mail.gmail.com> <d9c3f61a0907280011u525ba9e3k76f7746659b51784@mail.gmail.com> <8ac60eac0907280642h4700d7d5m95204a6e201281da@mail.gmail.com> <d9c3f61a0907280955q627669c8wc0bf20a729b14137@mail.gmail.com>

At Tue, 28 Jul 2009 20:55:40 +0400,
Pavel Shevaev wrote:
> > Is the application multithreaded?
> 
> Yes. And yes, I tried using helgrind as well and it discovered nothing...

Have you also tried DRD
<http://valgrind.org/docs/manual/drd-manual.html>? I'm not sure how
likely that is to help, but...

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

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