From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id SAA17471; Sat, 31 Jul 2004 18:35:48 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id SAA18028 for ; Sat, 31 Jul 2004 18:35:47 +0200 (MET DST) Received: from asmtp-a063f35.pas.sa.earthlink.net (asmtp-a063f35.pas.sa.earthlink.net [207.217.120.220]) by concorde.inria.fr (8.12.10/8.12.10) with ESMTP id i6VGZkSH032570 for ; Sat, 31 Jul 2004 18:35:47 +0200 Received: from 168-103-58-16.tcsn.qwest.net ([168.103.58.16] helo=dylan) by asmtp-a063f35.pas.sa.earthlink.net with asmtp (Exim 4.34) id 1Bqwpl-0004OD-BN for caml-list@inria.fr; Sat, 31 Jul 2004 09:35:45 -0700 Message-ID: <001b01c4771c$95f1d4e0$0201a8c0@dylan> From: "David McClain" To: "caml" Subject: [Caml-list] Moving up to 3.08 Date: Sat, 31 Jul 2004 09:36:46 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-ELNK-Trace: 7a0ab3eafc8cf994b22988ad1c62733440683398e744b8a464343fd1afab98bd52720d908f59cdf2387f7b89c61deb1d350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 168.103.58.16 X-Miltered: at concorde with ID 410BCA62.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; mcclain:01 dmcclain:01 aborting:01 ocaml-c:01 finalization:01 threading:01 incompatible:01 reclamation:01 mcclain:01 ocaml:01 ocaml:01 external:03 external:03 allocate:03 interface:03 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk For the first time in 5 years, recompiling my NML system to adopt a new release of OCaml is generating immediate Bus Errors and aborting when I try to start the freshly built NML system. OCaml runs just fine. So this tells me that something in the OCaml-C interface has changed. There is a fair amount of this used by NML to interface to everything in the outside universe for collecting data from external devices. Any hints about where to begin looking would be appreciated. Perhaps callback-registration, or finalization blocks? Or perhaps something in the threading machine is incompatible with Cocoa startup code? I haven't yet tried this process on Windows boxes. The first look was on Mac OS X. Cocoa is only used to the extent that I allocate some memory reclamation buffers for use in connecting to external AquaTerm servers using the Cocoa distributed variables interface, but no direct graphical operations are performed. I am doing this just before starting up the OCaml image, so there is another possible point of departure. David McClain Senior Corporate Scientist Avisere, Inc. +1.520.390.7738 (USA) david.mcclain@avisere.com ------------------- 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