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

toplevel threads #3137

Closed
vicuna opened this issue Jan 9, 2002 · 1 comment
Closed

toplevel threads #3137

vicuna opened this issue Jan 9, 2002 · 1 comment
Labels

Comments

@vicuna
Copy link

vicuna commented Jan 9, 2002

Original bug ID: 791
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)

Bug description

Full_Name: Matt Boyd
Version: Ocaml 3.04
OS: Windows 2000 and Unix
Submission from: 209.99.70.114 (209.99.70.114)

I'm probably doing something wrong, but I keep getting odd behavior when I
try to load the threads library. If I run the toplevel like this from a shell:

windows 2000: ocaml -I D:\ocaml\lib\threads
unix (linux): ocaml -I /usr/local/lib/ocaml/threads

It will start without a problem. Then I load the unix library followed by the
threads library:

#load "unix.cma";;
#load "threads.cma";;

This appears to work as well and it returns to a prompt. When I try to execute
any commands beyond this point, the toplevel quits with a segmentation fault
under Unix and just dies under Windows 2000.

I get similar behavior when I try compiling a custom toplevel.

Am I doing something wrong or is this just a quirk of using threads under the
3.04 toplevel?

@vicuna
Copy link
Author

vicuna commented Jun 11, 2002

Comment author: administrator

Fixed in 3.05.

@vicuna vicuna closed this as completed Jun 11, 2002
@vicuna vicuna added the bug label Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant