From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Giovanni Marzot <gmarzot@nortelnetworks.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Valgrind meets UML
Date: Thu, 23 Oct 2003 09:02:44 -0700 [thread overview]
Message-ID: <1066924964.12497.2.camel@ixodes.goop.org> (raw)
In-Reply-To: <3F97E849.1090700@nortelnetworks.com>
On Thu, 2003-10-23 at 07:40, Giovanni Marzot wrote:
> Can anyone confirm if the patches to valgrind mentioned below have found
> there way into the release?
They haven't. They were mostly slimy hacks to see what needed fixing,
rather than proper fixes. The good news is that I've been busily
incorporating proper fixes and redesigns into Valgrind, so the
development version should be capable of running uml unpatched soon.
> I wonder what "teaching valgrind about the false positives" entails.
Not everything Valgrind reports is an error. You can either generate a
suppression rule to tell V not to report it, or you can use annotations
in your program to tell V what's really going on.
J
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-10-24 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 14:40 [uml-devel] Re: Valgrind meets UML Giovanni Marzot
2003-10-23 16:02 ` Jeremy Fitzhardinge [this message]
2003-10-23 16:11 ` Giovanni Marzot
2003-10-23 16:45 ` Jeremy Fitzhardinge
2003-10-24 1:01 ` Jeff Dike
2003-10-24 8:22 ` Henrik Nordstrom
2003-10-25 1:02 ` Jeff Dike
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=1066924964.12497.2.camel@ixodes.goop.org \
--to=jeremy@goop.org \
--cc=gmarzot@nortelnetworks.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.