From: Mike Hamburg <hamburg@fas.harvard.edu>
To: caml-list@inria.fr
Subject: Elusive String.blit exception
Date: Wed, 2 Mar 2005 23:18:35 -0500 [thread overview]
Message-ID: <c03759ae1f681fa8e0d70601c81a8ad3@fas.harvard.edu> (raw)
I have a program which does not use the String module directly, which
very occasionally fails on Invalid_argument(String.blit). I have been
unable to track down the cause of this bug, and really don't know what
to make of it given that I'm not using the String module. The only
module that's used anywhere in that code which uses String (as far as I
can tell) is Printf. It seems very unlikely that Printf is failing,
given that it's tested more often than just about any other module in
the standard basis other than List.
Where could this exception be coming from? Is there any way to
automatically get a backtrace when my program dies on an exception?
Are there any other functions which use String.blit?
Mike Hamburg
next reply other threads:[~2005-03-03 4:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 4:18 Mike Hamburg [this message]
2005-03-03 9:52 ` [Caml-list] " Richard Jones
2005-03-03 10:15 ` Virgile Prevosto
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=c03759ae1f681fa8e0d70601c81a8ad3@fas.harvard.edu \
--to=hamburg@fas.harvard.edu \
--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