From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id B06717FA4D for ; Wed, 30 Jul 2014 15:11:21 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of christoph.hoeger@tu-berlin.de) identity=pra; client-ip=130.149.7.33; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="christoph.hoeger@tu-berlin.de"; x-sender="christoph.hoeger@tu-berlin.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of christoph.hoeger@tu-berlin.de) identity=mailfrom; client-ip=130.149.7.33; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="christoph.hoeger@tu-berlin.de"; x-sender="christoph.hoeger@tu-berlin.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail.tu-berlin.de) identity=helo; client-ip=130.149.7.33; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="christoph.hoeger@tu-berlin.de"; x-sender="postmaster@mail.tu-berlin.de"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApkBAMft2FOClQchm2dsb2JhbABZg2BXyziIXxYQAQEBAQEICQsJFCmEPAFFPRYYAwIBAgFYBgIBAYg+mRSnJY9phDQFon2RBWo X-IPAS-Result: ApkBAMft2FOClQchm2dsb2JhbABZg2BXyziIXxYQAQEBAQEICQsJFCmEPAFFPRYYAwIBAgFYBgIBAYg+mRSnJY9phDQFon2RBWo X-IronPort-AV: E=Sophos;i="5.01,764,1400018400"; d="scan'208";a="87614007" Received: from mail.tu-berlin.de ([130.149.7.33]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 30 Jul 2014 15:11:21 +0200 X-tubIT-Incoming-IP: 130.149.172.228 Received: from brego.uebb.tu-berlin.de ([130.149.172.228]) by mail.tu-berlin.de (exim-4.72/mailfrontend-5) with esmtpa for id 1XCTf5-0000uR-7r; Wed, 30 Jul 2014 15:11:20 +0200 Message-ID: <53D8EEF7.6060001@tu-berlin.de> Date: Wed, 30 Jul 2014 15:11:19 +0200 From: =?ISO-8859-15?Q?Christoph_H=F6ger?= Organization: Technische =?ISO-8859-15?Q?Universit=E4t_Berlin?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: caml-list@inria.fr X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Subject: [Caml-list] Segmentation fault due to uncaught type error -----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 - -- Christoph Höger Technische Universität Berlin Fakultät IV - Elektrotechnik und Informatik Übersetzerbau und Programmiersprachen Sekr. TEL12-2, Ernst-Reuter-Platz 7, 10587 Berlin Tel.: +49 (30) 314-24890 E-Mail: christoph.hoeger@tu-berlin.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlPY7vcACgkQhMBO4cVSGS+JuQCglLXD2Qt9SdvdndA3hGd2JVdw iLsAn2OsG/BVHfYwmhJ2knrrX33kVHEm =zvj1 -----END PGP SIGNATURE-----