From: "Sébastien Hinderer" <Sebastien.Hinderer@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] C, threads, callbacks, and corrupted local_roots
Date: Fri, 21 Jun 2019 13:38:35 +0200 [thread overview]
Message-ID: <20190621113835.GA28574@prajna.paris.inria.fr> (raw)
In-Reply-To: <8a6cb4e0-e3b2-437f-a7f7-c430170a9fdd@www.fastmail.com>
Hi again, Cédric,
> 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?
Yes, you are perfectly right, very sorry about that and many thanks for
having pointed this out.
I have just submitted https://github.com/ocaml/ocaml/pull/8759 as an
attempt to improve the situation.
> I guess this is the difference between libasmrun and libasmrund
Yes and also between ocamlrun and ocamlrund
> (I indeed have both installed), although objdump shows debug sections
> in both.
The difference is not so much in the debug symbols, rather in the fact
that, as the INSTALL files rightly explains, the debug version contains
assertions and sanity checks that the valinna versioon does not contain.
> 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.
Why did you try to link rather than using the runtime's executable,
actually?
Best wishes,
Sébastien.
next prev parent reply other threads:[~2019-06-21 11:38 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
2019-06-21 11:38 ` Sébastien Hinderer [this message]
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=20190621113835.GA28574@prajna.paris.inria.fr \
--to=sebastien.hinderer@inria.fr \
--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