From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: navin p <navinp1281@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>, gdb@sourceware.org
Subject: Re: Corruption in C++ constructor
Date: Thu, 14 Aug 2014 17:20:00 -0000 [thread overview]
Message-ID: <CAH6eHdRh2g5-pWf_+ahX27N4pfit0XtmPhn-4WPg6sTCFfJctA@mail.gmail.com> (raw)
In-Reply-To: <CAKVd3pWpoa+_Af76DBNYg5zauCKjnyMTjGdM=Htr7KrmEDcueg@mail.gmail.com>
On 14 August 2014 17:18, navin p wrote:
> Is this a corruption , how do i debug this ?
You can try rebuilding your code with -D_GLIBCXX_DEBUG compiler
option, which turns on debugging checks in the C++ standard library.
That might reveal a bug in your code.
You could also try using the sanitizer features in recent versions of GCC.
prev parent reply other threads:[~2014-08-14 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 16:18 navin p
2014-08-14 17:20 ` Jonathan Wakely [this message]
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=CAH6eHdRh2g5-pWf_+ahX27N4pfit0XtmPhn-4WPg6sTCFfJctA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=navinp1281@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