From: Jeremy Fitzhardinge <jeremy@goop.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] [Bug 98444] valgrind fails to run against user-mode-linux (UML) process - clone
Date: 3 Feb 2005 01:17:03 -0000 [thread overview]
Message-ID: <20050203011703.30244.qmail@ktown.kde.org> (raw)
In-Reply-To: <20050202220205.98444.das_deniz@yahoo.com>
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=98444
------- Additional Comments From jeremy goop org 2005-02-03 02:17 -------
Hm, nothing obvious sticks out. That clone() is basically just a fork() with no special options, which Valgrind has supported for a long time, so I'm not sure what's going on there. The warnings about tlsinfo and *_tidptr are spurious.
It seems the child process just jumps to 0x7 as soon as it starts running...
Is there any difference with --tool=none?
BTW, you're still going to get bitten by stack switching with memcheck and addrcheck.
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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:[~2005-02-03 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 21:02 [uml-devel] [Bug 98444] New: valgrind fails to run against user-mode-linux (UML) process - clone das deniz
2005-02-02 21:11 ` [uml-devel] [Bug 98444] " das deniz
2005-02-03 1:17 ` Jeremy Fitzhardinge [this message]
[not found] <bug-98444-50230@http.bugs.kde.org/>
2008-08-28 0:18 ` Steve VanDeBogart
2009-07-02 4:11 ` Nicholas Nethercote
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=20050203011703.30244.qmail@ktown.kde.org \
--to=jeremy@goop.org \
--cc=98444@bugs.kde.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox