Daniel Stenberg wrote:
>
> On Fri, 21 Dec 2001 David.Bentham_at_poole.siemens.co.uk wrote:

> > To me this all seems to point to a stack problem. The fact the fault moves
> > by removing a few valid executions from the execution path implies there is
> > nothing particularly nasty within socketerror() but delays the point at
> > which the stack craps out. I have also sort of assumed that the dodgy value
> > in the port number is due to stack corruption too.
>
> This does indeed sounds like some kind of stack problem. Have you measured
> how much stack it uses and much stack you have (left)?

There is a very high probability that this is a stack problem. I had a
similar problem with trio on QNX, where one array on the stack used some
100 Kb. The problem was fixed by making the array smaller.

I don't know what the default stack size on QNX is though.
Received on 2001-12-21