caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: oleg@okmij.org
To: paulfsnively@gmail.com
Cc: caml-list@inria.fr
Subject: [Caml-list] Delimcc.0 OPAM Package Difficulty on Mac OS X
Date: 12 Apr 2013 08:56:10 -0000	[thread overview]
Message-ID: <20130412085610.74136.qmail@www1.g3.pair.com> (raw)


> Unfortunately, testd0opt is my next headache: it crashes with a Bus Error on
> Darwin, but not on Debian Wheezy running in VirtualBox. VirtualBox doesn't
> do processor emulation, so the issue once again seems to be differences in
> the Darwin runtime environment from the Linux runtime environment. In the
> native context, my initial guess is that it may have something to do with
> stack alignment issues, but this is merely a guess.

I think Darwin and Ubuntu might be using different compilers (I think
Apple bet on LLVM/clang). Even when both system use GCC, chances are
they are of different versions, and some are more aggressive than
others (at optimization). The first thing to try is to compile
testd0opt without optimization (set -O0 or something like
that). Second, if there is a way to get a stack trace on seg fault
(e.g., via GDB) that could be helpful. 

BTW, it helps to compile stacks-native.c with the DEBUG
option. One can use either -DDEBUG or change
	#define DEBUG 0
at the beginning of the file so it reads "#define DEBUG 1". Now when
running the tesd0opt we should see more output. It would be good to
get the whole output of running tesd0opt.

And another thing: for native delimcc we don't have to use dynamic
linking. One may link in delimcc.cmx along with stacks-native.o
statically. Perhaps that might help.




             reply	other threads:[~2013-04-12  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12  8:56 oleg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-04-16  6:01 oleg
2013-04-09 11:08 oleg

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=20130412085610.74136.qmail@www1.g3.pair.com \
    --to=oleg@okmij.org \
    --cc=caml-list@inria.fr \
    --cc=paulfsnively@gmail.com \
    /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).