RE: [Valgrind-users] detect writing to TOC(?)

[Vincent Penquerc'h <Vin...@ar...>]

> The net is that I had stubbed a global *variable* symbol with a
> *function*.  Thus, the assignment to that variable was actually trying
> to write into the TOC (is that the correct term?).

If I understand what you meant, that would be .text.
That is, the first bytes of the function code would be overwritten.
Such space should be read only, so it's odd that Valgrind would
not pick that up.
Or I'm totally off.

-- 
Vincent Penquerc'h