"clipka" <nomail@nomail> wrote:
> To cut a long story short: This looks like a typical "wild pointer" to me, so> the underlying error could be *anywhere* in the code.
Linux? Sounds like a job for valgrind, but I don't know if that's practical for
something this large. I used it yesterday. A bad pointer started causing
problems in a completely unrelated spot. Took a couple minutes to solve with
valgrind.
- Ricky
