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.

Sign up for GitHub

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

Jump to bottom

Immortal threads? #3365

Closed
vicuna opened this issue May 30, 2002 · 2 comments
Closed

Immortal threads? #3365

vicuna opened this issue May 30, 2002 · 2 comments
Labels
bug

Comments

@vicuna
Copy link

vicuna commented May 30, 2002

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

Bug description

Full_Name: Chris Quinn
Version: 3.04
OS: linux rh6.2
Submission from: 212.42.169.63 (212.42.169.63)

Hello.

I'm not sure this is a bug but ...

If the program below is run and ^C'ed there remains still an outstanding
thread.
Uncommenting the signal setting and everything is fine.
Is this to be expected?

let sigwatch signo =
prerr_endline "signal received in thread"

let go () =
Unix.sleep 100000

let _ =
ignore(Thread.create go ());
(* Sys.set_signal Sys.sigint (Sys.Signal_handle sigwatch);*)
Unix.sleep 100000
@vicuna
Copy link
Author

vicuna commented Jun 3, 2002

Comment author: administrator

I'm not sure this is a bug but ...
If the program below is run and ^C'ed there remains still an outstanding
thread.
Uncommenting the signal setting and everything is fine.
Is this to be expected?

It works OK here, with the development version of OCaml and under
Mandrake 7.2.

Could you identify the thread that wouldn't die? If you do "ps" while
the program is running, you should see four processes executing your
program, hopefully with numbers N, N+1, N+2 and N+3. If N+1 is the
one that doesn't die, it looks like a bug in the version of
LinuxThreads you're using. (Thread N+1 is the "thread manager thread"
used internally by LinuxThreads.)

  • Xavier Leroy

@vicuna
Copy link
Author

vicuna commented Jun 11, 2002

Comment author: administrator

Not enough info.

@vicuna vicuna closed this as completed Jun 11, 2002
@vicuna vicuna added the bug label Mar 19, 2019
bobzhang pushed a commit to rescript-lang/ocaml that referenced this issue Mar 23, 2019
@chenglou
[Super errors] Clean up super_typemod.ml (ocaml#3365)
3bf168b 
* [Super errors] Expose previously shadowed `report_error`

Used by super_typemod.ml

* [Super errors] Clean up super_typemod

Defer work to the newly exposed `Typemod.super_report_error_no_wrap_printing_env`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vicuna