I'm not using Obj. I am unmarshalling. I have 'ulimit -s unlimited' set and I'm unmarshalling with the exact same binary that did the marshalling. The unmarshalling itself finishes ok but I guess the segfault could be caused when accessing the resulting data structure?
I'm marshalling data which contains a DynArray which in turn contains functional values, but I'm using [Marshal.No_sharing; Marshal.Closures] and I haven't changed the code between marshalling and unmarshalling. On Thu, Nov 4, 2010 at 8:25 PM, Raphael Proust <raphla...@gmail.com> wrote: > Le jeudi 04 novembre 2010 21:19:33, Jamie Brandon a écrit : >> Is there an authoritative list anywhere of the possible causes for >> segfaults in ocaml? I'm not using the FFI or -unsafe and I have ruled >> out overflowing the c stack and allocating large strings/arrays. I'm >> using ocaml 3.09.3 with extlib, netclient, json-static, xml-light, str >> and no compilation options. > > Unmarshalling can cause segfaults and Obj.magic too. > > -- > _______ > Raphaël > > _______________________________________________ > 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 > _______________________________________________ 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
