> 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
I'm having trouble tracking down some segmentation faults with a C
extension. I can see where it's failing but don't know how to fix
it. Basically, my python programme builds a pair of large tuples of
tuples. I want to unpack these tuples and process them. The code in
question looks something l
