Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unix and nums can not be Dynlinked together (Assert_failure in bytecomp/dll.ml) #6802

Closed
vicuna opened this Issue Mar 3, 2015 · 3 comments

Comments

Projects
None yet
1 participant
@vicuna
Copy link
Collaborator

vicuna commented Mar 3, 2015

Original bug ID: 6802
Reporter: erwan
Status: closed (set by @xavierleroy on 2017-02-16T14:18:32Z)
Resolution: fixed
Priority: normal
Severity: minor
Platform: amd32,amd64
OS: debian
OS Version: wheezy
Version: 4.02.1
Target version: 4.03.0+dev / +beta1
Fixed in version: 4.03.0+dev / +beta1
Category: runtime system and C interface
Has duplicate: #6108

Bug description

unix and nums can not be Dynlinked together from a toplevel

Raises
Exception: Assert_failure ("bytecomp/dll.ml", 110, 4)

Steps to reproduce

ocaml
#use "topfind";;
#require "dynlink";;
#require "unix";; (* works without this #require )
Dynlink.allow_unsafe_modules true;; (
nums requires this *)
Dynlink.loadfile "./.opam/4.02.1+PIC/lib/ocaml/nums.cma";;

Additional information

tried also on 4.00.0, and 3.12.0

I've initially mentioned this as a note there:
#6108

But I'm unsure it's actually related.

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Mar 3, 2015

Comment author: @alainfrisch

I doubt the problem is related to unix and/or num, rather to the fact that Dynlink is not supported in the toplevel (as far as I know). Or can you provide an example that fails to dynlink unix and nums from a standalone program (not a toplevel)?

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Mar 3, 2015

Comment author: erwan

No (well, I do, but with programs that use Topmain, so I guess it does not count :).

I didn't know Dynlink was not officially supported in the toplevel, thanks for the info.

How should I know that BTW? Anyway it looks very close to work.

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Dec 6, 2015

Comment author: @xavierleroy

Commit [trunk 8e6606d] causes Dynlink to fail cleanly if loaded from the toplevel loop.

@vicuna vicuna closed this Feb 16, 2017

@vicuna vicuna added the stdlib label Mar 14, 2019

@vicuna vicuna added this to the 4.03.0 milestone Mar 14, 2019

@vicuna vicuna added the bug label Mar 20, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.