From: "Yaron Minsky" <yminsky@cs.cornell.edu>
To: "OCaml List" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] segfault in 3.10.0
Date: Wed, 1 Aug 2007 20:39:28 -0400 [thread overview]
Message-ID: <891bd3390708011739r254c6297o78fddf60c6d78ea4@mail.gmail.com> (raw)
In-Reply-To: <1A56E60C-26B2-42E0-BDE1-21DA8F92406D@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2548 bytes --]
It might be useful to post the stack backtrace.
y
On 8/1/07, Andres Varon <avaron@gmail.com> wrote:
>
> Another bit of information is that I can segfault the program even
> for the most trivial input, with minimal computations involved. And
> when run under gdb, the backtrace lists pure OCaml function calls,
> and always the same one.
>
> On Aug 1, 2007, at 5:10 PM, Andres Varon wrote:
>
> > Hello Everyone,
> >
> > Has anyone observed sudden segfaults in OCaml 3.10.0 amd-64 under
> > linux? I have this program that has been run for quite a while
> > without any segfault (almost a year). It may run for weeks at a
> > time in parallel in our cluster, using as many as 256 processors at
> > a time. We delayed updating to 3.10.0 due to the changes in camlp4,
> > but the day before yesterday I worked on it, upgraded, and suddenly
> > a lot of the nightly unit tests in 64 bits fail with a segfault (a
> > LOT of them), when every test passed clean with 3.09.3. None of the
> > tests for other architectures fail though (windows, mac os X intel
> > and 32-bit ppc). One down side is that we have C structures
> > wrapped, so one may blame our program.
> >
> > However, efence and valgrind show no sign of problem, and the fact
> > that we have been using those structures for a while, and many test
> > iterations have passed for many inputs, and not only us, but many
> > people in other computers have compiled and run our program without
> > having segfaults ... I'm doubtful.
> >
> > Unfortunately I have been unable to compile 3.10.0 for 64 bits in
> > our g5 under Mac OS X, so that architecture remains untested. The
> > segfault is occurring within the OCaml code. Any pointer would be
> > greatly appreciated, or suggestions of tools that could help us
> > hunting this down ... I'm awfully clueless about what to do
> > today ... and it's been just a couple of days :-(
> >
> > best,
> >
> > Andres
> > _______________________________________________
> > Caml-list mailing list. Subscription management:
> > http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> > Archives: http://caml.inria.fr
> > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > Bug reports: http://caml.inria.fr/bin/caml-bugs
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> 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: 3447 bytes --]
next prev parent reply other threads:[~2007-08-02 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 21:10 Andres Varon
2007-08-01 22:27 ` [Caml-list] " Andres Varon
2007-08-02 0:39 ` Yaron Minsky [this message]
2007-08-02 5:05 ` Markus Mottl
2007-08-02 15:41 ` Andres Varon
2007-08-02 16:46 ` Alain Frisch
2007-08-02 17:31 ` Andres Varon
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=891bd3390708011739r254c6297o78fddf60c6d78ea4@mail.gmail.com \
--to=yminsky@cs.cornell.edu \
--cc=caml-list@yquem.inria.fr \
/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