From: Andreas Fredriksson <deplinenoise@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: C++ code on Gentoo
Date: Wed, 17 Aug 2005 13:47:30 +0200 [thread overview]
Message-ID: <3212b1a80508170447766f9ba4@mail.gmail.com> (raw)
In-Reply-To: <loom.20050816T200236-899@post.gmane.org>
On 8/16/05, James <wireless@tampabay.rr.com> wrote:
> The code for nvwa-0.5 was added to try to get robust debugging
> (memory) working, but, alas I'm certainly not strong on C++ code,
> let alone some body else's C++ code.
Try valgrind. It's an excellent memory instrumentation system which
can trace back programming mistakes with complete callstacks of the
offending site if you compile with debugging symbols. Last time I
looked, a fairly recent version was in portage.
Good luck,
Andreas
--
And I hate redundancy, and having different functions for the same thing.
- Linus Torvalds on linux-kernel
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-08-17 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 19:18 [gentoo-user] C++ code on Gentoo James
2005-08-16 20:51 ` Bryce Verdier
2005-08-17 14:18 ` [gentoo-user] " James
2005-08-17 15:43 ` Uwe Thiem
2005-08-17 18:29 ` Ciaran McCreesh
2005-08-17 11:47 ` Andreas Fredriksson [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=3212b1a80508170447766f9ba4@mail.gmail.com \
--to=deplinenoise@gmail.com \
--cc=gentoo-user@lists.gentoo.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