Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0006048OCamlOCaml documentationpublic2013-06-23 06:172013-06-24 10:04
Reportersesquized 
Assigned To 
PrioritynormalSeverityminorReproducibilityN/A
StatusresolvedResolutionno change required 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0006048: It is not documented what happens when you nest caml_acquire_runtime_system()
DescriptionThe section 19.10.1 of the manual describes the caml_acquire_runtime_system() and caml_release_runtime_system().

I don't see where the text addresses what happens if you call acquire more than once from the same thread.

I looked at the Windows code and it appeared that you just need to match the number of releases to the number of acquires and you can acquire the lock more than once safely. (But I'm not certain and don't know if it's true for other OSs/build environments.)

It would be good if the topic was explained specifically.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0009605)
xleroy (administrator)
2013-06-24 10:04

The behavior is very much unspecified: under Windows, it might work because the master lock is reentrant, but under POSIX systems it is very likely to deadlock at the second caml_release_runtime_system(). So, don't do that.

- Issue History
Date Modified Username Field Change
2013-06-23 06:17 sesquized New Issue
2013-06-24 10:04 xleroy Note Added: 0009605
2013-06-24 10:04 xleroy Status new => resolved
2013-06-24 10:04 xleroy Resolution open => no change required


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker