Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Pavel Shevaev <pacha.shevaev@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Trying to spot memory corruption with core dump
Date: Tue, 28 Jul 2009 06:58:00 -0000	[thread overview]
Message-ID: <8ac60eac0907272358n7cd27407va0a9982ea4d466bc@mail.gmail.com> (raw)
In-Reply-To: <d9c3f61a0907272344q697efd1ag1d9b073be4df94b0@mail.gmail.com>

On Mon, Jul 27, 2009 at 11:44 PM, Pavel Shevaev<pacha.shevaev@gmail.com> wrote:

> 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.

Indeed.

> 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.

Depending on which platform you are on, you may have tools available
which will get you to the problem *much* faster (or at least the
computer will be looking for the problem while you can do something
else :-)

On Linux/ix86 and x86_64, nothing beats Valgrind (for finding heap corruption).
On Solaris, try libumem. Most other UNIX platforms have various heap
checking libraries as well.

Cheers,
-- 
Paul Pluzhnikov


  reply	other threads:[~2009-07-28  6:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28  6:44 Pavel Shevaev
2009-07-28  6:58 ` Paul Pluzhnikov [this message]
2009-07-28  7:12   ` Pavel Shevaev
2009-07-28 13:43     ` Paul Pluzhnikov
2009-07-28 16:55       ` Pavel Shevaev
2009-07-28 17:32         ` Michael Snyder
2009-07-28 21:51         ` Samuel Bronson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8ac60eac0907272358n7cd27407va0a9982ea4d466bc@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=gdb@sourceware.org \
    --cc=pacha.shevaev@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox