From: Jeff Dike <jdike@addtoit.com>
To: Nicholas Nethercote <njn25@cam.ac.uk>
Cc: Tom Hughes <thh@cyberscience.com>,
dbahi@enterasys.com, user-mode-linux-devel@lists.sourceforge.net,
valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] Re: [uml-devel] Re: UML and valgrind
Date: Thu, 05 Aug 2004 11:24:44 -0400 [thread overview]
Message-ID: <200408051524.i75FOiCi002455@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 05 Aug 2004 10:28:00 BST." <Pine.LNX.4.60.0408051026120.21344@hermes-1.csi.cam.ac.uk>
njn25@cam.ac.uk said:
> To summarise: you seem to be confident there won't be any problems,
> and Tom's not so sure. I'm not sure either, but the threads/signals/
> syscalls stuff is the part of Valgrind I understand the least. I
> would say, just don't be shocked if you do this and weird things
> start happening :)
Fair enough. I'd just point out that this worked fine a couple of years ago,
so there's some basis for my confidence. OTOH, that patch was never merged,
so possibly that basis has disappeared.
But I'd say that this is worth looking into, since valgrinding the kernel
would be an immensely useful thing to be able to do.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
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:[~2004-08-05 14:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 4:13 [uml-devel] UML and valgrind Bahi, David
2004-08-03 2:47 ` [uml-devel] " D. Bahi
2004-08-03 5:17 ` Jeff Dike
2004-08-03 9:31 ` [Valgrind-users] " Nicholas Nethercote
2004-08-03 14:50 ` Jeff Dike
2004-08-03 14:31 ` Nicholas Nethercote
2004-08-03 17:50 ` Jeff Dike
2004-08-03 17:33 ` D. Bahi
2004-08-03 19:31 ` Jeff Dike
2004-08-03 20:12 ` D. Bahi
2004-08-04 7:47 ` Tom Hughes
2004-08-03 22:04 ` Nicholas Nethercote
2004-08-04 7:52 ` Tom Hughes
2004-08-04 15:10 ` Jeff Dike
2004-08-04 15:35 ` Jeff Dike
2004-08-04 14:58 ` Tom Hughes
2004-08-04 18:00 ` Jeff Dike
2004-08-04 17:57 ` Tom Hughes
2004-08-04 21:02 ` Jeff Dike
2004-08-05 9:28 ` Nicholas Nethercote
2004-08-05 13:15 ` D. Bahi
2004-08-05 15:24 ` Jeff Dike [this message]
2004-08-03 19:40 ` Jeff Dike
2004-08-04 1:09 ` Nuno Silva
2004-08-04 2:47 ` D. Bahi
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=200408051524.i75FOiCi002455@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=dbahi@enterasys.com \
--cc=njn25@cam.ac.uk \
--cc=thh@cyberscience.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=valgrind-users@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 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 NNTP newsgroup(s).