From: Yaron Minsky <yminsky@janestreet.com>
To: Mark Shinwell <mshinwell@janestreet.com>
Cc: caml-list@inria.fr, Ivan Gotovchits <ivg@ieee.org>
Subject: Re: [Caml-list] Core breaks backtraces
Date: Wed, 18 Dec 2013 07:01:58 -0500 [thread overview]
Message-ID: <CACLX4jR=hYJcv=RAue1RSwphWESQ6MYRCEcKT8HTNz37Mp-e9A@mail.gmail.com> (raw)
In-Reply-To: <CAM3Ki74o90G=XVrTYFFHZPVri+0taZ5J4RHRUinWQcweb=3ecg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]
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 Dec 18, 2013 6:45 AM, "Mark Shinwell" <mshinwell@janestreet.com> wrote:
> 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
>
[-- Attachment #2: Type: text/html, Size: 2960 bytes --]
next prev parent reply other threads:[~2013-12-18 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 6:17 Ivan Gotovchits
2013-12-18 11:44 ` Mark Shinwell
2013-12-18 12:01 ` Yaron Minsky [this message]
2013-12-19 4:00 ` Ivan Gotovchits
2013-12-19 9:07 ` Jeremie Dimino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACLX4jR=hYJcv=RAue1RSwphWESQ6MYRCEcKT8HTNz37Mp-e9A@mail.gmail.com' \
--to=yminsky@janestreet.com \
--cc=caml-list@inria.fr \
--cc=ivg@ieee.org \
--cc=mshinwell@janestreet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox