> It's not worth staring at code to try to figure out things like that.
> Run it under gdb, examine the relevant data objects when it crashes
> and see what's broken (e.g. some pointer is unexpectedly null), then
> set a conditional breakpoint that stops execution when that incorrect
> condition ha
Daryl <[EMAIL PROTECTED]> writes:
> The inner loop runs a few hundred times (263) then fails with a
> segmentation fault. I've trolled through the documentation online and
> in the various .h files but can't seem to find anything.
>
> Anybody have an idea what really obvious foolish thing I'm doi
