From: "Markus Mottl" <markus.mottl@gmail.com>
To: "David Brown" <caml-list2@davidb.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Segfault in caml_oldify_local_roots.
Date: Thu, 31 Aug 2006 16:11:27 -0400 [thread overview]
Message-ID: <f8560b80608311311k5fc1c82fy66db6a17146d2663@mail.gmail.com> (raw)
In-Reply-To: <44F69EF1.5000702@davidb.org>
On 8/31/06, David Brown <caml-list2@davidb.org> wrote:
> Turns out that if I'd read it more carefully, I should have realized that
> Gzip.close_out will also close the underlying handle. Apparently calling
> close_out twice on the same handle messes things up enough to segfault the
> garbage collector.
This is a known bug which is fixed in the current CVS-release:
http://caml.inria.fr/mantis/view.php?id=4039
Normally, closing an already closed channel a second time should not
cause any problems.
Regards,
Markus
--
Markus Mottl http://www.ocaml.info markus.mottl@gmail.com
prev parent reply other threads:[~2006-08-31 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 6:32 David Brown
2006-08-31 8:33 ` [Caml-list] " David Brown
2006-08-31 20:11 ` Markus Mottl [this message]
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=f8560b80608311311k5fc1c82fy66db6a17146d2663@mail.gmail.com \
--to=markus.mottl@gmail.com \
--cc=caml-list2@davidb.org \
--cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).