From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id CCC5F7EC6E for ; Thu, 19 Dec 2013 05:00:14 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of ivg@ieee.org) identity=pra; client-ip=209.85.215.53; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="ivg@ieee.org"; x-sender="ivg@ieee.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of ivg@ieee.org designates 209.85.215.53 as permitted sender) identity=mailfrom; client-ip=209.85.215.53; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="ivg@ieee.org"; x-sender="ivg@ieee.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-la0-f53.google.com) identity=helo; client-ip=209.85.215.53; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="ivg@ieee.org"; x-sender="postmaster@mail-la0-f53.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Au8DAF9uslLRVdc1nGdsb2JhbABZg0ODWIVtnSuKJIhfIXQWDgEBAQEBBg0JCRQogiUBAQEDASADSwsFCwkCDgoNHQICNAEFAQoSBhMSh14DCQgEAQiVJo9ii3wIA5IpA4cGF40YgUcvBAeCbAI1gRMEiT2OWYEwhRWJYkGEXA X-IPAS-Result: Au8DAF9uslLRVdc1nGdsb2JhbABZg0ODWIVtnSuKJIhfIXQWDgEBAQEBBg0JCRQogiUBAQEDASADSwsFCwkCDgoNHQICNAEFAQoSBhMSh14DCQgEAQiVJo9ii3wIA5IpA4cGF40YgUcvBAeCbAI1gRMEiT2OWYEwhRWJYkGEXA X-IronPort-AV: E=Sophos;i="4.95,511,1384297200"; d="scan'208,217";a="41652687" Received: from mail-la0-f53.google.com ([209.85.215.53]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 19 Dec 2013 05:00:13 +0100 Received: by mail-la0-f53.google.com with SMTP id mc6so220438lab.12 for ; Wed, 18 Dec 2013 20:00:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:from:subject :date:to; bh=mwfDNSibuxVXqURDKQyjrLN1COfllUbtCyeCF6u7b+k=; b=G9OIMb6oah5AkmvP65GDIEk6LGuRh1OKKZcQp6UXLy1juwEALCORZKOLV27CN8O5Li x0GhaoyIrn+0atq9+2hP5Tf2hs0kdJ6mNey0hc2GtS5WD7HEnoIQ12N2zhOdmSIJYE/1 VBGrWVbylZM8TJchDAM/Yx4VPc7cZ8Rt8wY4Fwn7lalDFhgj+kRQ0NGNhxJq2p6XBGP3 QJaMZIiejWT5YUvEfW6HseS4R0+zQT5e23a47SoudNvNVbEpl5fEkoK/G3BzKupgripv 9plUeq7E7hC/4yP24M3MnVImW8N6hl80cmMsn+m6BVcaC90nymcP+hmZAf9K5PXD0vau 7nZw== X-Gm-Message-State: ALoCoQmPLBjM63m0fca4F1d6p8lAYAbJjTChLPMyAO8KwVkbEL+oN42rta3osEuLEWmMr8MRbMsO X-Received: by 10.152.120.231 with SMTP id lf7mr114505lab.36.1387425612573; Wed, 18 Dec 2013 20:00:12 -0800 (PST) Received: from [192.168.0.70] (ip-46-73-177-196.bb.netbynet.ru. [46.73.177.196]) by mx.google.com with ESMTPSA id sd11sm1791083lab.2.2013.12.18.20.00.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Dec 2013 20:00:11 -0800 (PST) References: <874n661y5e.fsf@golf.niidar.ru> In-Reply-To: Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary=Apple-Mail-8B54FFE0-C3DE-47DE-A275-09782F8905A7 Message-Id: <2FBC5172-E53A-4E0C-913F-C4F17BD49482@ieee.org> Cc: Mark Shinwell , "caml-list@inria.fr" X-Mailer: iPad Mail (11B554a) From: Ivan Gotovchits Date: Thu, 19 Dec 2013 08:00:14 +0400 To: Yaron Minsky Subject: Re: [Caml-list] Core breaks backtraces --Apple-Mail-8B54FFE0-C3DE-47DE-A275-09782F8905A7 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable > On 18 =C4=C5=CB. 2013 =C7., at 16:01, Yaron Minsky wrote: >=20 > Do you need to set OCAMLRUNPARAM to trigger the problem? I'm curious bec= ause Core enables backspaces by default.=20 >=20 No, I didn't.=20 > It would be great if you can post precise steps for reproducing this, alo= ng with the platform details, on the bug tracker: >=20 > https://github.com/janestreet/core_kernel/issues >=20 > To say the obvious, I use core both on Linux and the Mac and have never s= een this, so I suspect something about your setup is tickling this issue. >=20 I'll do my best, but it is only observable with my program. I cannot reprod= uce it, using simple steps.=20 It'll be helpful if you provide some clues on where to dig in core. I'm new= to core and it is overwhelmingly large. It will be easier for me to trace = the problem, if I understand what core do with the backtraces. >> On Dec 18, 2013 6:45 AM, "Mark Shinwell" wrot= e: >> 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. >>=20 >> 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? >>=20 >> 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. >>=20 >> Mark >>=20 >> -- >> 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 --Apple-Mail-8B54FFE0-C3DE-47DE-A275-09782F8905A7 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable


On 18 =D0=B4=D0= =B5=D0=BA. 2013 =D0=B3., at 16:01, Yaron Minsky <yminsky@janestreet.com> wrote:

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

No, I didn't. 

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.

I'll do my best, but it is only obse= rvable with my program. I cannot reproduce it, using simple steps. 

It'll be helpful if you provide some clues on where = to dig in core. I'm new to core and it is overwhelmingly large. It will be = easier for me to trace the problem, if I  understand what core do with= the backtraces.

On Dec 18, 2013 6:45 AM, "Mark Shinwell" <mshinwell@janestreet.com> w= rote:
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.<= 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?  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:
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
= --Apple-Mail-8B54FFE0-C3DE-47DE-A275-09782F8905A7--