Summary: | user-allocated stack is inaccessible even after thread finishes | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Aleksander Salwa <A.Salwa> |
Component: | memcheck | Assignee: | Julian Seward <jseward> |
Status: | REPORTED --- | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 3.1.1 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | test case |
Description
Aleksander Salwa
2006-03-28 14:25:50 UTC
Created attachment 15333 [details]
test case
Resetting state of whole malloc'ed block that contains this stack isn't a good solution. Proper solution should also handle stacks that are made of part of malloc'ed block or are statically allocated. Realistically I think the prospects for fixing this are not good, since we don't know how to make our stack-tracking heuristics sophisticated enough. |