Re: [Caml-list] Segmentation fault due to uncaught type error

[Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>]

On 2014/07/30 22:11, Christoph Höger wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Dear OCaml users/developers,
> 
> I am developing a rather large codebase using OCaml and somewhat
> stressing the type system in the process. I already triggered a bug
> which I could reproduce with a small example and reported it.
> 
> This one is different. In short: I have a test case that compiles just
> fine, even though my program contains a (stupid) type error. Resulting
> is a runtime crash of the generated OCaml code (while attempting to
> access a record field, a computed pointer points to noman's land).
> 
> The thing is: this time, I don't see a way to reduce the code to a
> smaller size. It is probably doable, but it's also likely that the
> reduced code will not trigger the error. So the whole process will
> probably take a long time. Time, I (unfortunately) do not have.
> 
> On the other hand, I would consider this kind of a bug a very severe
> problem in any statically typed language. So I really want to help out
> to track down and reproduce this bug. I just cannot do it alone.
> 
> As a first step, if anyone wants to work on this issue, I would help
> out to compile the program in the first place. It has some
> dependencies which could be cut-off, and others that need to be
> installed. Hopefully, most deps could be removed, though.
> 
> Anyone interested?
> 
> Christoph


If there is really a bug in the compiler, this is indeed bad.
This happens once in a while, and we fix that as soon as possible.
A good idea would be to check with a recent version of the compiler,
for instance the current state of the 4.02 branch, which is now pretty stable.

  svn co http://caml.inria.fr/svn/ocaml/version/4.02

Otherwise, if you know what the type error should be, you can try to explain it with
a snippet of code. Sometimes what the type should be is not so clear :-)

And bug reports go to the bug tracking system.
  http://caml.inria.fr/mantis/
It’s better if you can cut it down to something understandable, but if you can’t
we’ll still look into it.

Jacques Garrigue