https://bugs.kde.org/show_bug.cgi?id=373046
Bug ID: 373046
Summary: Stacks registered by core are never deregistered
Product: valgrind
Version: 3.12 SVN
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: philippe.waroqui...@skynet.be
Target Milestone: ---
(see master bug 323020)
* thread stacks are registered using m_stacks.c VG_(register_stack),
but are never deregistered.
syswrap-<machine>-linux.c are all calling VG_(register_stack).
However, these stacks are never deregistered: the only call to
VG_(deregister_stack) is in scheduler.c (for the client request).
So, an application with many threads creation/destruction might end up with
a bunch of "dead" client stacks registered in m_stacks.c
(these dead stacks might then point anywhere, as the client thread memory
might have been recycled e.g. for malloc).
Also, it is unclear if and where the darwin implementation registers
the thread stacks.
--
You are receiving this mail because:
You are watching all bug changes.
