From: Aleksey Nogin <nogin@cs.caltech.edu>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] [3.06] Is there a difference in weak array implementation between the bytecode and native code?
Date: Tue, 16 Dec 2003 22:45:12 -0800 [thread overview]
Message-ID: <3FDFFB78.4010500@cs.caltech.edu> (raw)
I am looking for help tracking a Weak-related bug.
For couple of years already our group is having trouble tracking some
very elusive bug. Once in a while (quite rarely) in some big Weak
array-based code something goes wrong (we get a wrong value). Sometimes
the bug is completely random - an identical run does not reproduce it.
Sometime it is reproducible in a specific case, but whenever something
changes (e.g. any sort of debugging code is added), it goes away. It
seems that the bug only occurs in bytecode, but never occurs in native
code. So far we've been seeing it only under 3.06 (there are some other
issues preventing us from switching to 3.07).
I do not know whether this is a bug in our code, in OCaml code, or our
code is making some assumptions about the OCaml runtime that are
reasonable, but not true...
Anyway, I am wondering - is there some difference between the bytecode
and native code in how the Weak module behaves (in 3.06)? Anything that
could shed some light on why it is the case that we only see this weird
bug under bytecode?
TIA!
--
Aleksey Nogin
Home Page: http://nogin.org/
E-Mail: nogin@cs.caltech.edu (office), aleksey@nogin.org (personal)
Office: Jorgensen 70, tel: (626) 395-2907
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
reply other threads:[~2003-12-17 6:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3FDFFB78.4010500@cs.caltech.edu \
--to=nogin@cs.caltech.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;
as well as URLs for NNTP newsgroup(s).