Summary: | valgrind fails to run against user-mode-linux (UML) process - clone | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | das deniz <das_deniz> |
Component: | general | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | crash | CC: | njn, user-mode-linux-devel, vandebo-valgrind |
Priority: | NOR | ||
Version: | 2.3 CVS | ||
Target Milestone: | --- | ||
Platform: | RedHat Enterprise Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | complete valgrind log of crash |
Description
das deniz
2005-02-02 22:02:05 UTC
Created attachment 9396 [details]
complete valgrind log of crash
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. There is now a wiki page that describes how to get valgrind to work with User Mode Linux here: http://uml.jfdi.org/uml/Wiki.jsp?page=ValgrindingUML I'm closing crashing and similar bugs that are more than two years old. If you still see this problem with Valgrind 3.4.1 please reopen the bug report. Thanks. |