Do you need to set OCAMLRUNPARAM to trigger the problem? I'm curious because Core enables backspaces by default.
It would be great if you can post precise steps for reproducing this, along with the platform details, on the bug tracker:
https://github.com/janestreet/core_kernel/issues
To say the obvious, I use core both on Linux and the Mac and have never seen this, so I suspect something about your setup is tickling this issue.
On 18 December 2013 06:17, Ivan Gotovchits <ivg@ieee.org> wrote:
> I've tried a fabulous core library and it broke my exceptions :)
> All backtraces are now look like this
>
> backtrace:
> Raised at file "map.ml", line 117, characters 16-25
> Called from file "lib/conv.ml", line 256, characters 19-50
>
> Next, if I enable backtrace recording with OCAMLRUNPARAM environment
> variable and compile a .d.byte version of my application than on an
> exception occurrence core eats all my memory thus killing my machine.
>
> Any clues, what happens?
>
> P.S. removing Core.Std from project fixes all issues.
> P.P.S. My application is rather large and uses lots of processes and
> lwt, moreover it enables lwt backtracing via ocamlbuild plugin.
>
> P.P.P.S . By using core I mean just opening Core.Std in a an empty
> module, this is enough to broke my system.
Are you always building bytecode? Which version of the
compiler, which operating system, and on which hardware
platform? Does this happen when you compile for native code?
I suggest you also try copying the contents of core/lib/std.ml
into your empty module and bisecting to determine which
of the Core modules causes the failure.
Mark
--
Caml-list mailing list. Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs