From: rixed@happyleptic.org
To: caml-list@inria.fr
Subject: Re: [Caml-list] C, threads, callbacks, and corrupted local_roots
Date: Fri, 21 Jun 2019 12:51:49 +0200 [thread overview]
Message-ID: <8a6cb4e0-e3b2-437f-a7f7-c430170a9fdd@www.fastmail.com> (raw)
In-Reply-To: <20190621073031.GA26636@prajna.paris.inria.fr>
> re:the debug
> runtime, at least upstream it is now enabled by default so I would
> expect opam to provide it with the compiler for recent versions, rather
> than in a separate package.
This makes sense.
Does it mean that the INSTALL.doc, which instruct to manually change the compilation flag and rebuild (see https://github.com/ocaml/ocaml/blob/trunk/INSTALL.adoc#if-something-goes-wrong) is not up to date?
I guess this is the difference between libasmrun and libasmrund (I indeed have both installed), although objdump shows debug sections in both.
Indeed, when I compile without -fPIC and link with libasmrund on Linux it seems to run in some debug mode; ie. it does print additional debug strings, but there are no more debug symbols and it seems to be compiled with optimisations on all the same. Also, it crash at the very same line with the very same 0xfff in local root address.
Under macos I can;t link with libasmrun nor libasmrund as the linker then complains about missing symbols such as _caml_extern_sp. That's why I've been linking with libasmrun_shared in the first place. This so file does not seem to come with a debug version.
next prev parent reply other threads:[~2019-06-21 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 18:03 rixed
2019-06-21 7:30 ` Sébastien Hinderer
2019-06-21 10:51 ` rixed [this message]
2019-06-21 11:38 ` Sébastien Hinderer
2019-06-21 12:21 ` rixed
2019-06-21 14:00 ` Sébastien Hinderer
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=8a6cb4e0-e3b2-437f-a7f7-c430170a9fdd@www.fastmail.com \
--to=rixed@happyleptic.org \
--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).