caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "David McClain" <dmcclain1@mindspring.com>
To: "caml" <caml-list@inria.fr>
Subject: [Caml-list] Moving up to 3.08
Date: Sat, 31 Jul 2004 09:36:46 -0700	[thread overview]
Message-ID: <001b01c4771c$95f1d4e0$0201a8c0@dylan> (raw)

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


                 reply	other threads:[~2004-07-31 16:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='001b01c4771c$95f1d4e0$0201a8c0@dylan' \
    --to=dmcclain1@mindspring.com \
    --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;
as well as URLs for NNTP newsgroup(s).