From: David Allsopp <dra-news@metastack.com>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] OCaml-4.02.1 on windows XP
Date: Fri, 5 Dec 2014 22:22:03 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9E9748EA9@Remus.metastack.local> (raw)
In-Reply-To: <CALGm1VhYs3Djx0AM=A5Zsz_QLtnmYTNGCHhZkxQarTyWTL9xZA@mail.gmail.com>
Damien Doligez wrote:
> > Fatal error: exception Cmi_format.Error(_)
>
> I don't know how this exception escaped (it is supposed to be caught by the
> compiler) but it looks like you have some old .cmi files lying around that
> were compiled by your previous version of OCaml. You should remove them,
> and also the .cmo, .cmx, etc. and recompile everything (including any
> third-party libraries that you might have installed).
Amusingly, I wrote out what I thought the trace would be in my original reply and then thought it was too much detail so deleted it :o)
I think that what will be escaping is:
Topmain.main -> Toplevel.loop -> Toplevel.initialize_toplevel_env -> Compmisc.initial_env -> Compmisc.open_implicit_module -> Env.open_pers_signature -> Env.find_pers_struct -> Env.read_pers_struct -> Cmi_format.read_cmi -> *bang*
That whole trace occurs before the main [while true do] loop in Toploop.loop and so before the general exception handler mapping to Errors.report_error is "installed".
AFAICT, an invalid CAMLLIB/OCAMLLIB is the only "sane" (i.e. easy-to-do) way that this can happen.
David
prev parent reply other threads:[~2014-12-05 22:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 10:27 Alain Coste
2014-12-01 10:57 ` David Allsopp
2014-12-01 15:46 ` Alain Coste
2014-12-01 15:52 ` Fabrice Le Fessant
2014-12-01 10:59 ` Fabrice Le Fessant
2014-12-01 12:00 ` Daniel Bünzli
2014-12-05 18:49 ` Damien Doligez
2014-12-05 22:22 ` David Allsopp [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=E51C5B015DBD1348A1D85763337FB6D9E9748EA9@Remus.metastack.local \
--to=dra-news@metastack.com \
--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).