Hello, In the past week I had several bugs that while gdb pointed to a place X, the actual place was several instructions prior to that position.
For example the following error message I had to an off by one bug: *** glibc detected *** ./test_parser: malloc(): memory corruption (fast): 0x0000000001ddad50 *** The instruction set that I was at, when glibc raised this exception was a lot further then the original position of the function that caused it have been executed. Only by using valgrind, that I could find the exact location and figure out, that it was another function that had the problem. How does the modern memory management system is working then, that it takes so much time for the problem to surface ? Thanks, Ido
_______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
