I have a personnal marked dislike for xml-light; one of the reason
being that it is tied together using duct-tape and generous sprinkling
Obj.magic. Probably not the cause of your problem but, and again, who
knows.
We (Jane street) have a patched version that does not use Obj.magic;
the main reason that I haven't pushed for us to upstream these patches
is that I'd rather see Xml-light die in favour of something that
adheres better to the xml standards (like xmlm).
It might be intersting for you to run your app in gdb and sent the
backtrace of the segfault. Valgrind could also be very useful here but
it is not for the faint of heart.
very quick guide to gdb (although I am sure you know):
_ 1) Make sure your program is compiled with -g
_ 2) gdb ./my_pgm
> run
.... (boom!)
> bt
On Thu, Nov 4, 2010 at 4:19 PM, Jamie Brandon
<ja...@scattered-thoughts.net> wrote:
> 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.
>
> Cheers
>
> Jamie
>
> _______________________________________________
> 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
