From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id AFC017EC6E for ; Wed, 18 Dec 2013 13:02:00 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of yminsky@janestreet.com) identity=pra; client-ip=38.105.200.229; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yminsky@janestreet.com"; x-sender="yminsky@janestreet.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of yminsky@janestreet.com designates 38.105.200.229 as permitted sender) identity=mailfrom; client-ip=38.105.200.229; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yminsky@janestreet.com"; x-sender="yminsky@janestreet.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@tot-dmz-mxout1.janestreet.com) identity=helo; client-ip=38.105.200.229; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yminsky@janestreet.com"; x-sender="postmaster@tot-dmz-mxout1.janestreet.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsCAJ+NsVImacjlnGdsb2JhbABZg0JJDKVtiiSIUoESHg4BAQEBAQYWCTyCJQEBAQMBQAEBLAsBBAsLBAcDCg0hIhIBBQEKEgYTEodeAwkIAwIIpGuLEYRSAQWODQOHBhEGjRiBdgQHhDaJR45TgTCOdxgphHU X-IPAS-Result: ApsCAJ+NsVImacjlnGdsb2JhbABZg0JJDKVtiiSIUoESHg4BAQEBAQYWCTyCJQEBAQMBQAEBLAsBBAsLBAcDCg0hIhIBBQEKEgYTEodeAwkIAwIIpGuLEYRSAQWODQOHBhEGjRiBdgQHhDaJR45TgTCOdxgphHU X-IronPort-AV: E=Sophos;i="4.95,507,1384297200"; d="scan'208";a="49533201" Received: from mx5.janestreet.com (HELO tot-dmz-mxout1.janestreet.com) ([38.105.200.229]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 18 Dec 2013 13:01:59 +0100 Received: from tot-oib-smtp1.delacy.com ([172.27.22.15] helo=tot-smtp) by tot-dmz-mxout1.janestreet.com with esmtp (Exim 4.76) (envelope-from ) id 1VtFp9-0002ZA-AR for caml-list@inria.fr; Wed, 18 Dec 2013 07:01:59 -0500 Received: from tot-dmz-mxgoog1.delacy.com ([172.27.224.14] helo=mxgoog2.janestreet.com) by tot-smtp with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VtFp9-0001Xo-9V for caml-list@inria.fr; Wed, 18 Dec 2013 07:01:59 -0500 Received: from mail-la0-f48.google.com ([209.85.215.48]) by mxgoog2.janestreet.com with esmtp (Exim 4.76) (envelope-from ) id 1VtFp9-0000VH-3c for caml-list@inria.fr; Wed, 18 Dec 2013 07:01:59 -0500 Received: by mail-la0-f48.google.com with SMTP id n7so3747377lam.7 for ; Wed, 18 Dec 2013 04:01:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=E/8rKFSEiBy46LpOtxu1qeW+JUTF2yyF5qlv6CUP4GE=; b=h6ux0qDhi0Ty9T3rPYN+o6311/9Ry/vnlHOTRL64s9LoyFMeSESAMwoA64Bnuk7VQk 5sC9hVVDsv0ezWGQ9pxMW3SVKS9RU/nU6BFGCVoiZ16GBr1SnWyNRRB9x3Ns5DreJRDa MiQy7WkBhq3NnN1DqV8jSBZXqfCdhUDkNrsNQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=E/8rKFSEiBy46LpOtxu1qeW+JUTF2yyF5qlv6CUP4GE=; b=ZEQrbGgOfqPpFwdkinne1S2oi80irzTbuPckASoURo8Nw1zT2oPD7cpNaIKCLwhQLG 1Dhd6uGVq4SlFAw6jVKww6yUb7cn8PkbgECtE8zOoQmBaU+jSO7E9s3Vu/SS9Pdt/Szr k+tpangobUJPj5JE/LjgiDQsbU0Du5V48WuurosF76RCJWSZqxBbwp+mAltATrGUvDBF Oe2AAP2BVqi6NwaHXXpLreI6oXAeuHWq/40OFWFniu9xwL78h0h5dmP2NStpwiiMrB46 PEqvvt4r1QguxMpaNduw4zkQhuputIES69Oi7osgwI4hU1fCKtpvoUGROT0I4hvh53hm tDmA== X-Gm-Message-State: ALoCoQlzr27l6ncNnEcpXm0geEbMYg195Lg4tblOR5mRbqUJpmD3Xhe0fHL3KmsMBtxERdUNpExuROjYcI3DNGXTKcBk4Cliq9x5Z7hVZQGfo5YYmGCpiqqGLdVLQzCa0cE4WBNvmtAWVujShrGLLXQpQ9JJQ7x2dg== X-Received: by 10.112.131.103 with SMTP id ol7mr671346lbb.72.1387368118322; Wed, 18 Dec 2013 04:01:58 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.131.103 with SMTP id ol7mr671342lbb.72.1387368118203; Wed, 18 Dec 2013 04:01:58 -0800 (PST) Received: by 10.112.1.69 with HTTP; Wed, 18 Dec 2013 04:01:58 -0800 (PST) Received: by 10.112.1.69 with HTTP; Wed, 18 Dec 2013 04:01:58 -0800 (PST) In-Reply-To: References: <874n661y5e.fsf@golf.niidar.ru> Date: Wed, 18 Dec 2013 07:01:58 -0500 Message-ID: From: Yaron Minsky To: Mark Shinwell Cc: caml-list@inria.fr, Ivan Gotovchits Content-Type: multipart/alternative; boundary=047d7b3a86dedbcc2804edcdcf16 Subject: Re: [Caml-list] Core breaks backtraces --047d7b3a86dedbcc2804edcdcf16 Content-Type: text/plain; charset=ISO-8859-1 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" wrote: > On 18 December 2013 06:17, Ivan Gotovchits 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 > --047d7b3a86dedbcc2804edcdcf16 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Do you need to set OCAMLRUNPARAM to trigger the problem?=A0 = I'm curious because Core enables backspaces by default.=A0

It would be great if you can post precise steps for reproduc= ing 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&quo= t; <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
>
> =A0 backtrace:
> =A0 Raised at file "m= ap.ml", line 117, characters 16-25
> =A0 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.<= br> >
> 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? =A0Which version of the
compiler, which operating system, and on which hardware
platform? =A0Does 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. =A0Subscription management and archives:
ht= tps://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
--047d7b3a86dedbcc2804edcdcf16--