caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sebastien Mondet <sebastien.mondet@gmail.com>
To: "Richard W.M. Jones" <rich@annexia.org>
Cc: Ashish Agarwal <agarwal1975@gmail.com>, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] segfault in simple program with 4.02 native
Date: Fri, 5 Sep 2014 18:01:11 -0400	[thread overview]
Message-ID: <CALScVY=ArQ1t0YW2j7PKw4+jZ=ZA2sm55HdUC9HGu8hTjKvwoA@mail.gmail.com> (raw)
In-Reply-To: <20140905215626.GB3416@annexia.org>

[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]

Rich, please just `git pull`, Core has been removed from the deps few
seconds ago.




On Fri, Sep 5, 2014 at 5:56 PM, Richard W.M. Jones <rich@annexia.org> wrote:

> On Fri, Sep 05, 2014 at 05:33:11PM -0400, Ashish Agarwal wrote:
> > https://github.com/agarwal/ocaml402_error
> >
> > The above link contains a simple program that segfaults when compiling
> with
> > ocamlopt 4.02. Byte code doesn't segfault, nor does native code with
> 4.01.
> >
> > This is the minimal example I could come up with. It uses atdgen and is
> > sensitive to the exact fields in the .atd file. Removing any of the
> fields
> > leads to correctly functioning code.
> >
> > I've only tested on Mac OS X so far.
> >
> > In the context of my full code, I observed another behavior also. Instead
> > of a segfault, I would get random non-ascii characters printed for the
> > value of postgres.host, and it would be different on repeated runs of the
> > program (I didn't even recompile in between). I can't seem to reproduce
> > this behavior, only getting the segfault now.
>
> I made a best effort to compile that, but I don't have some of
> the gazillion dependencies.  So instead I have a suggestion:
>
> What happens if you increase the stack limit?
>
> Rich.
>
> --
> Richard Jones
> Red Hat
>
> --
> 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: 2440 bytes --]

  reply	other threads:[~2014-09-05 22:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05 21:33 Ashish Agarwal
2014-09-05 21:50 ` Andy Ray
2014-09-05 21:56 ` Richard W.M. Jones
2014-09-05 22:01   ` Sebastien Mondet [this message]
2014-09-05 22:06   ` Ashish Agarwal
2014-09-05 22:13     ` Richard W.M. Jones
2014-09-05 22:18       ` Richard W.M. Jones
2014-09-05 22:36         ` Török Edwin
2014-09-05 22:39         ` Martin Jambon
2014-09-05 23:39           ` Ashish Agarwal
2014-09-05 23:59             ` Martin Jambon
2014-09-06  0:12           ` Jeremy Yallop
2014-09-06  5:51             ` Martin Jambon
2014-09-06  6:00               ` Milan Stanojević
2014-09-06  7:46                 ` Frédéric Bour
2014-09-06 19:15                   ` Martin Jambon
2014-09-06 19:08                 ` Martin Jambon
2014-09-06 20:31                   ` David MENTRÉ
2014-09-06 21:57                     ` Martin Jambon
2014-09-07  7:34                       ` David MENTRÉ
2014-09-07 18:47               ` Alain Frisch
2014-09-08  1:28                 ` Martin Jambon
2014-09-13 10:26                   ` Martin Jambon
2014-09-14  7:41                     ` Martin Jambon
2014-09-05 22:18       ` Christoph Höger

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='CALScVY=ArQ1t0YW2j7PKw4+jZ=ZA2sm55HdUC9HGu8hTjKvwoA@mail.gmail.com' \
    --to=sebastien.mondet@gmail.com \
    --cc=agarwal1975@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=rich@annexia.org \
    /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;
as well as URLs for NNTP newsgroup(s).