You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 1805 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
type idref =
{ id :
mutable (((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((
(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((
... snip several more pages of (s ...
(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((
((((Fatal error: exception Stack_overflow
Strangely, the file crash.ml can be compild with ocamlc -pp camlp4r and loaded
into the top level without any problems.
I get this behaviour in both 3.06 and 3.07beta2.
The text was updated successfully, but these errors were encountered:
Original bug ID: 1805
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Jim Farrand
Version: 3.06/3.07beta2
OS: Debian Gnu/Linux
Submission from: 81-86-132-151.dsl.pipex.com (81.86.132.151)
This is actually a bug effecting camlp4 included with OCaml. Is this the right
place to submit such a bug?
Here is a shell history showing the bug:
$ cat crash.ml
type idref = { id : mutable ! 'a . 'a -> 'a };
$ ocamlmktop -o ocaml /usr/local/ocaml-3.07beta2/lib/ocaml/camlp4/camlp4r.cma
$ ./ocaml
Objective Caml version 3.07+beta 2
#use "crash.ml" ;
type idref =
{ id :
mutable (((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((
(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((
... snip several more pages of (s ...
(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((
((((Fatal error: exception Stack_overflow
Strangely, the file crash.ml can be compild with ocamlc -pp camlp4r and loaded
into the top level without any problems.
I get this behaviour in both 3.06 and 3.07beta2.
The text was updated successfully, but these errors were encountered: