The stack traces given by Memcheck (or another tool) seem to have the wrong function name in them. Whats happening?
Occasionally Valgrind stack traces get the wrong function names. This is caused by glibc using aliases to effectively give one function two names. Most of the time Valgrind chooses a suitable name, but very occasionally it gets it wrong. Examples we know of are printing bcmp instead of memcmp, index instead of strchr, and rindex instead of strrchr.
Related Questions
- I know that I have several user profiles configured in Netscape, but Im not being given the option to select a profile when I launch Netscape. Whats wrong?
- Either I did do it right, was given the wrong yeast energiser or I had the wrong recipe?
- Why don I get function names when Memory Advisor prints stack traces?
