Summary: | JIT asserts inside valgrind | ||
---|---|---|---|
Product: | WebKit | Reporter: | Balazs Kelemen <kbalazs> |
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED WONTFIX | ||
Severity: | Normal | CC: | ashl1future, chanika, zherczeg |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | Linux |
Description
Balazs Kelemen
2010-05-13 06:42:14 PDT
same here. I've created a very minimal test case: http://chani.ca/webkit/valgrind/ all I have to do is make two should* calls and I get the assert failure. I have found a solution: use "--smc-check=all". This is needed because the JIT::linkCall function (and some other JIT staff) modifying the jitted code, so valgrind must check self modification. Alternatively we could use valgrind's client request mechanism. That would be cheaper, but I am dubious about how the apple folks would feel about to introduce valgrind into the codebase (we should have at least a build option, and a define for valgrind). I think we can leave with the --smc-check=all option, so I set this as wontfix. |