caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sami Liedes <sliedes@cc.hut.fi>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Assertion failure in ocamlrund
Date: Tue, 31 May 2005 04:15:30 +0300	[thread overview]
Message-ID: <20050531011530.GJ4700@sk2-4.tky.hut.fi> (raw)
In-Reply-To: <20050527192631.GF4700@sk2-4.tky.hut.fi>

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

On Fri, May 27, 2005 at 10:26:31PM +0300, Sami Liedes wrote:

> After having ocamlrun segfault on my program (only when running with
> OCAMLRUNPARAM=b, without b it reports an uncaught Not_found exception)
> I compiled the debugging version of it, and this is what I get:
> 
> file freelist.c; line 123 ### Assertion failed: wo_sz >= 1

Hi again,

I think I have narrowed down at least part of the problem now. It is
related to a file descriptor leak in the code; why this would cause
the above-mentioned assertion failure, I don't know, but I'd guess
it's not handled somewhere (symbol loading?).

Or perhaps that assertion failure is unrelated to the crash that
happens when running the non-debug version of ocamlrun with
OCAMLRUNPARAM=b. Somehow it seems that ocamlrund gets the assertion
failure _much_ quicker than the non-debug version segfaults.

Apparently this also causes the confusing claim by the runtime that in
the event of an unhandled exception a backtrace cannot be produced
because the program was compiled without debug symbols.

	Sami

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2005-05-31  1:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27 19:26 Sami Liedes
2005-05-27 21:13 ` [Caml-list] " Damien Doligez
2005-05-27 22:03   ` Sami Liedes
2005-05-31  1:15 ` Sami Liedes [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=20050531011530.GJ4700@sk2-4.tky.hut.fi \
    --to=sliedes@cc.hut.fi \
    --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;
as well as URLs for NNTP newsgroup(s).