Modern Linux memory management
ik
idokan at gmail.com
Thu Jan 26 16:34:28 IST 2012
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cs.huji.ac.il/pipermail/linux-il/attachments/20120126/35610e7c/attachment.html>
More information about the Linux-il
mailing list