From: John Max Skaller <skaller@ozemail.com.au>
To: caml-list@inria.fr
Subject: [Caml-list] Weird bug
Date: Thu, 09 May 2002 00:58:41 +1000 [thread overview]
Message-ID: <3CD93D21.6030505@ozemail.com.au> (raw)
In-Reply-To: <20020507154306.B18437@pauillac.inria.fr>
I've just produced some strange behaviour in my program.
I get "Not_found" exception.. when I turn on my programs
debug tracing, the program works.
Some trivial input that previously worked now causes my
program to core dump. [Heh .. some test input
to the compiler works fine .. but when I add
print "Hello world\n";
to the end, my compiler core dumps ..
the same statement compiles find in other places,
and it compiles fine with debug tracing on]
So .. this sounds like memory corruption to me.
But the only way a "nice" ocaml program should
be able to corrupt memory is by a stack overflow.
[My code is "nice" NO arrays, NO magic, NO C routines
called .. its a compiler, all list and hashtable stuff --
the only nasty thing is that I have ocamlopt.opt --rectypes]
Previously I noticed that this was trapped
(an actual infinite recursion gracefully exited
with a stack overflow message .. nice!!)
I find it hard to believe my program has exceeded
any sensible limitations (some of the typing
in the parser is really flogging the ocaml compiler
.. 20 second compilation .. was 1 second ..
but the generated code should be small).
Question: any known bugs in ocaml that could cause this?
Question: I previously found a serious bug with polymorphic
variants in Ocaml 3.02. The code that triggered the bug
works fine with 3.01 and with 3.04. Has that bug been
identified and fixed (or was I just lucky ..and now unlucky again)?
Question: is stack overflow always trapped?
It seems unlikely that I have an infinite recursion .. since
turning on debug output shouldn't change the flow
of control [though it is possible .. since the output
is controlled by a flag ..]
--
John Max Skaller, mailto:skaller@ozemail.com.au
snail:10/1 Toxteth Rd, Glebe, NSW 2037, Australia.
voice:61-2-9660-0850
-------------------
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
next prev parent reply other threads:[~2002-05-08 14:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 11:26 [Caml-list] OCaml-announcements Oliver Bandel
2002-05-07 13:43 ` Xavier Leroy
2002-05-07 14:42 ` Remi VANICAT
2002-05-07 16:05 ` Matt Armstrong
2002-05-08 14:58 ` John Max Skaller [this message]
2002-05-08 15:45 ` [Caml-list] Weird bug John Max Skaller
2002-05-08 20:10 ` [Caml-list] Bug in typing polymorphic variants found John Max Skaller
2002-05-10 15:02 ` Luc Maranget
2002-05-10 16:43 ` John Max Skaller
2002-05-13 6:46 ` Jacques Garrigue
2002-05-13 9:21 ` Luc Maranget
2002-05-13 16:35 ` John Max Skaller
2002-05-13 16:05 ` John Max Skaller
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=3CD93D21.6030505@ozemail.com.au \
--to=skaller@ozemail.com.au \
--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