From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jeff Dike <jdike@addtoit.com>
Cc: Dan Kegel <dank@kegel.com>,
linux-kernel@vger.kernel.org, Robert Walsh <rjwalsh@durables.org>
Subject: Re: Valgrinding the kernel?
Date: Fri, 06 Jul 2007 11:00:46 -0700 [thread overview]
Message-ID: <468E834E.6020906@goop.org> (raw)
In-Reply-To: <20070706172513.GD10670@c2.user-mode-linux.org>
Jeff Dike wrote:
> Don't think so. With what I get on FC5 (valgrind-3.1.0), I get this:
>
> ==31913== Jump to the invalid address stated on the next line
> ==31913== at 0x9: ???
> ==31913== by 0xBEC1599A: ???
> ==31913== by 0x696C2F69: ???
> ==31913== Address 0x9 is not stack'd, malloc'd or (recently) free'd
> ==31913==
> ==31913== Process terminating with default action of signal 11 (SIGSEGV): dumping core
>
> UML is cloning a thread in order to test the host's ptrace. However,
> it looks like valgrind is branching to 0x9 for some reason.
>
How far into the run does this happen? Immediately, or after a while?
> This particular bit is going to be problematic for other reasons, but
> if valgrind ever looks like it has a chance of working, I can work
> around that in UML.
>
Hm. I haven't touched Valgrind in a couple of years, and I suspect
people haven't been as mean to it as I was being. It might be time I
gave it some love. (I've also been thinking about porting it to be a
Xen guest so that we can Valgrind whole virtual machines - but that's a
different story.)
J
next prev parent reply other threads:[~2007-07-06 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 4:14 Valgrinding the kernel? Dan Kegel
2007-07-06 5:44 ` Jeremy Fitzhardinge
2007-07-06 17:25 ` Jeff Dike
2007-07-06 17:30 ` Dan Kegel
2007-07-06 19:42 ` Jeff Dike
2007-07-06 19:51 ` Jeremy Fitzhardinge
2007-07-06 21:09 ` Jeff Dike
2007-07-06 18:00 ` Jeremy Fitzhardinge [this message]
2007-07-06 19:04 ` 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=468E834E.6020906@goop.org \
--to=jeremy@goop.org \
--cc=dank@kegel.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjwalsh@durables.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