From: skaller <skaller@users.sourceforge.net>
To: Denis Bueno <dbueno@gmail.com>
Cc: Richard Jones <rich@annexia.org>,
OCaml Mailing List <caml-list@inria.fr>
Subject: Re: Re: [Caml-list] Trouble with doubly-linked, circular list using lazy evaluation
Date: Wed, 25 Oct 2006 22:10:58 +1000 [thread overview]
Message-ID: <1161778258.6194.1.camel@rosella.wigram> (raw)
In-Reply-To: <6dbd4d000610250359n3c73cd7eh230e7911ab70d74a@mail.gmail.com>
On Wed, 2006-10-25 at 06:59 -0400, Denis Bueno wrote:
> On 10/25/06, Richard Jones <rich@annexia.org> wrote:
> > I can confirm a seg fault on OCaml 3.09.1, Linux/AMD64. Have you
> > thought about filing a bug here: http://caml.inria.fr/mantis/main_page.php
>
> Reported. It's issue 0004141.
Also 3.09.3+rc1 has the segfault linux/AMD64.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2006-10-25 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 1:46 Denis Bueno
2006-10-25 9:01 ` [Caml-list] " Richard Jones
2006-10-25 10:59 ` Denis Bueno
2006-10-25 12:10 ` skaller [this message]
2006-11-17 15:02 ` Damien Doligez
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=1161778258.6194.1.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=dbueno@gmail.com \
--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