Martin Stjernholm wrote:
"Stephen R. van den Berg" srb@cuci.nl wrote:
It just means that I need to compile from a different tree (which I wanted to avoid), since keeping the binaries, but not the accompanying sources tends to make gdb navigation unusable.
I usually don't bother - backtraces are still fairly sane, and you can still inspect data without problems. It's only line numbers and source listings that can be a little bit off.
Yes, but if that happens in (for me) unfamiliar sections of the code, it gets kind of messy if I cannot use "list" to find my way around at frame levels (it then sort of feels like in nethack, when you drank a potion of confusion).
So even though the error really was pretty big, it had very rarely any observable effect. Very insidious.
Just my luck then :-).
(Another effect of the bug was that Pike.count_memory missed some things and returned a little bit too low count.)
We'll see. I have another pretty big bug lined up, I'm hoping that through some magic this might fix the other one too. But judging from the description it doesn't seem likely. More on that later.