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

Double close_out cause segfaults at the next gc major operation #4062

Closed
vicuna opened this issue Jul 16, 2006 · 1 comment
Closed

Double close_out cause segfaults at the next gc major operation #4062

vicuna opened this issue Jul 16, 2006 · 1 comment

Comments

@vicuna
Copy link

vicuna commented Jul 16, 2006

Original bug ID: 4062
Reporter: @yakobowski
Status: closed (set by @damiendoligez on 2006-07-17T08:01:36Z)
Resolution: fixed
Priority: normal
Severity: major
Version: 3.09.2
Category: ~DO NOT USE (was: OCaml general)
Duplicate of: #4039

Bug description

(my first real bug :-) )

    Objective Caml version 3.09.2

let ch = open_out "essai" in close_out ch; close_out ch;;

Segmentation fault

    Objective Caml version 3.10+dev8 (2006-06-26)

let ch = open_out "essai" in close_out ch; close_out ch;;

Segmentation fault

(This is an up-to-date cvs version, in which I've unmasked a function in
printf.mli. But I don't think the problem comes from this)

In the two cases above, if the segfault does not occur at once, calling
Gc.compact() and Gc.full_major() does. I've also gotten a signal 10 once.

Now comes the funny part :

    Objective Caml version 3.10+dev1 (2005-10-26)

let ch = open_out "essai" in close_out ch; close_out ch;;

  • : unit = ()

Gc.compact();;

  • : unit = ()

Gc.full_major();;

  • : unit = ()

--
Boris

@vicuna
Copy link
Author

vicuna commented Jul 17, 2006

Comment author: @damiendoligez

deja reporte et fixe dans la branche 3.09 (#4039)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant