[Valgrind-users] Valgrind reporting memory errors inside allocated regions?

[Tae L. K. <ur...@pr...>]

Hi,

I tried running my program under Valgrind to look for any pesky memory corruption bugs, but in addition to taking an inordinately long time to start up (e.g. creating the font atlas takes 3 minutes), I get a lot of errors about invalid reads and writes such as those listed in this attachment. What really baffles me is that they show that the reads happened in a region of allocated memory.

My initial guess is that it has something to do with my program handling memory very weirdly: some of the code switches the stack pointer in order to implement coroutines. In fact, Valgrind does warn of this.

My code is here in case anyone actually wants to try it:
https://gitlab.com/nagakawa/tdr

– T