You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: