Version française
Home     About     Download     Resources     Contact us    
Browse thread
Causes for segfaults
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Till Varoquaux <till@p...>
Subject: Re: [Caml-list] Causes for segfaults
That's an odd backtrace.
As far as I can tell you have compiled everything fine yet it tells me
that run_query is blowing up in a subcall to caml_ml_close_channel
(which is the underlying c call for close_in and close_out).

I might be reading this bt wrong. Otherwise there's something fishy
with your stack. Whatever it is, I am very confused by this all. Would
you mind posting your code to see if other people can reproduce the
problem?

Cheers,
Till

On Mon, Nov 8, 2010 at 9:26 AM, Jamie Brandon
<jamie@scattered-thoughts.net> wrote:
>> If it is, perhaps try to limit it and try again in bytecode to see
>> if the Segmentation Fault is transformed into a Stack Overflow.
>
> Marshalling is not tail-recursive, so I will always get a stack
> overflow marshalling this much data. Setting ulimit -s unlimited
> prevents this but also obscures the current problem.
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>