From: Andrew Haley <aph@redhat.com>
To: Srivatsan Ramanujam <juggernautvatsan@yahoo.com>
Cc: Neil Ferguson <nferguso@eso.org>, gcc-help@gcc.gnu.org
Subject: Re: Valgrind - exact leak location.
Date: Thu, 26 Oct 2006 12:34:00 -0000 [thread overview]
Message-ID: <17728.43862.416496.871273@zebedee.pink> (raw)
In-Reply-To: <20061026123153.11951.qmail@web57115.mail.re3.yahoo.com>
Please don't top-post.
> --- Andrew Haley <aph@redhat.com> wrote:
>
> > Srivatsan Ramanujam writes:
> > > Hi Neil,
> > >
> > > Thanks for your inputs.
> > > Well by "exact location of error" I meant the
> > line
> > > number in my program file where the error
> > occured.
> > >
> > > As you can see
> > >
> > > "ABCParser::parseString()(stl_vector.h:501)"
> > >
> > > it says the error occured inside the function
> > > parseString() but it doesn't indicate which line
> > > number inside this function.
> >
> > Line 501.
Srivatsan Ramanujam writes:
> sin't line 501 inside stl_vector.h?
> That simply indicates the overloading of [] operator
> for a vector.
>
> line number 501 inside my program merely sets a value
> for an INTEGER variable.
Well, that is the best that is known to the compiler. It might be
correct; in any case it's all the information we have.
It might be worth rebuilding without optimization to get a more
accurate idea of what's going on.
Andrew.
next prev parent reply other threads:[~2006-10-26 12:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 6:32 Srivatsan Ramanujam
2006-10-26 10:04 ` Andrew Haley
2006-10-26 11:44 ` William Gallafent
2006-10-26 11:57 ` Neil Ferguson
2006-10-26 12:10 ` Srivatsan Ramanujam
2006-10-26 12:25 ` Andrew Haley
2006-10-26 12:32 ` Srivatsan Ramanujam
2006-10-26 12:34 ` Andrew Haley [this message]
2006-10-26 12:37 ` Srivatsan Ramanujam
2006-10-26 12:38 ` John Love-Jensen
2006-10-26 12:40 ` Srivatsan Ramanujam
2006-10-26 13:34 ` Valgrind - used gdb Srivatsan Ramanujam
2006-10-26 13:51 ` John Love-Jensen
2006-10-26 13:58 ` Srivatsan Ramanujam
2006-10-26 14:34 ` John Love-Jensen
2006-10-26 14:51 ` Neil Ferguson
2006-10-26 14:58 ` Srivatsan Ramanujam
2006-10-26 14:06 ` Including static libraries Sameer Naik
2006-10-26 14:20 ` Brian Budge
2006-10-26 12:14 ` Valgrind - exact leak location Srivatsan Ramanujam
2006-10-26 16:06 Kaz Kylheku
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=17728.43862.416496.871273@zebedee.pink \
--to=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=juggernautvatsan@yahoo.com \
--cc=nferguso@eso.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).