https://bugs.kde.org/show_bug.cgi?id=374940
Bug ID: 374940
Summary: i386: Stack access at -1(%%esp)
Product: valgrind
Version: 3.12 SVN
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Hi,
the code of libev uses "lock; orb %0,-1(%%esp)" as a memory guard. memcheck
complains.
In the libev author's opinion, this is a bug in valgrind as it should recognize
that this is a guard instruction which accesses legitimate (if uninitialized)
memory, and whose result isn't actually used for anything.
Would it be possible to each memcheck not to do that?
--
You are receiving this mail because:
You are watching all bug changes.
