On 4/29/2011 9:41 AM, Steve Schveighoffer wrote:
I'll mention that I just was debugging some stuff in
Linux for dcollections, and the line numbers for the unit
tests given by gdb were off by a couple of lines (I had the
same feelings you are having, how is this possible). That
was just inside the unit tests. In the actual code, the
line numbers were correct. What's more, when I would step
over lines in gdb, the program would jump *back* some lines
when there was no loop in the code.
I wouldn't trust that GDB is giving you accurate
info.
My recommendation -- try using writeln debugging if
possible.
-Steve
Actually, it looks like a case of function pointers getting
corrupted and pointing to places they shouldn't. The reason they
point to the code segment at all is because only the low order bits
are getting corrupted, so they land in the same general area as
they're supposed to.
|
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
