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

[Tom H. <th...@cy...>]

In message <1059661265.907.15.camel@pc>
        Paul A. Clarke <pa...@us...> wrote:

> 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?).

I assume by TOC you mean the symbol table, in which case the answer
is no, that isn't what it is trying to do. What it is trying to do is
write to the text segment of the program - ie the actual code.

Basically assigning to a global variable will get the address of that
variable and then try and write the assigned value to that address. In
this case when the linker resolved the address of the symbol it
actually gets the address of the code for the function and the program
therefore tries to write to that address and fails.

Tom

-- 
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/