Hacker News Reader

Huh, crazy. It's def tracked accesses straddling a stack frame boundary before for me.

It's not a stack frame boundary, though; it's just jumping between two objects in the same frame.

the default valgrind engine, memcheck, is a heap checker and doesn't find stack overruns.

In valgrind 3.7.0, you can use the experimental engine exp-sgcheck to look for stack and global overruns. ( valgrind command line parameter --tool=exp-sgcheck ). It is experimental and doesn't always work, but might have in this case.

that's surprising because there is a leaked pointer