lists on #include?
I (and a few others) have been battling with very similar errors for a few
weeks. We're using 7.6.50, so it's not likely to be the same problem, but
it seems very strange that so many of us are experiencing these problems
at the (relatively) same time.
I'm completely stumped as to my next course of action. At first I thought
it was because of some custom C-code, but I've had the problem without
that involved as well.
Bill
> Looks like it's an ordinary malloc() call that dies, and that's a
> sure sign of corrupted memory which can be extremely time-consuming
> to find. Recompiling Pike with memory debug options or using valgrind
> are possible options but perhaps best left for a Pike developer.
>
> ...
>
> Anyway, before we conclude that Pike itself is faulty it would help
> to know whether the Pike binary we have available for download
> misbehaves in the same way. Understandably you will not have your
> custom --with-pgsql switch active but hopefully that won't prevent
> you from running a test.
|