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

Folks, could you please share any tips on spotting possible memory
corruption by examining the core dump?

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

Somebody told me I could examine +-200 bytes of the memory where the
last exception happened but I don't really understand what I can find
there. For me it's just the raw amount of bytes...

Thanks in advance.

-- 
Best regards, Pavel


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28  6:44 Pavel Shevaev [this message]
2009-07-28  6:58 ` Paul Pluzhnikov
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=d9c3f61a0907272344q697efd1ag1d9b073be4df94b0@mail.gmail.com \
    --to=pacha.shevaev@gmail.com \
    --cc=gdb@sourceware.org \
    /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