I’m new to OCaml and have been struggling to set up a simple TCP server that stays open and can be killed or interrupted with Ctrl-C. Here's where I'm at withLwt_io.establish_server_with_client_address`: let establish_server port f = (* Create a new socket *) let default_protocol = 0 in let s…

@seanpoulter I am able to terminate the program with Ctrl+C with fst (Lwt.task ()) uncommented. What environment are you running this in (shell, OS, anything else noteworthy)?

Thanks @antron . I think I’ve worked it out to be ocaml/dune#1480 . I’ve got a Macbook that I’ve recently setup with dune 1.4.0. I’ve narrowed it down to only happening when I run: dune exec ./main.exe It responds to Ctrl-c when I run: dune build ./file.exe _build/default/file.exe

Yea, thanks. It was just realizing that you had to opam update before opam is aware of the new versions. I had tried opam install dune and opam upgrade dune and kept 1.4.0. :laughing: Thanks for the help and nudge in the right direction! :clap:

App doesn't respond to Ctrl-C / SIGINT / Signals when running dune exec

Learning

antron November 20, 2018, 2:15am 4

You may have already done this, but try upgrading to Dune 1.5.0. It fixed:

Unblock signals in processes started by dune (link)

Topic		Replies	Views
Dune built executable killed by zsh on macOS Ecosystem opam , dune	11	2876	January 20, 2021
Lwt - how to catch exceptions raised by signal handlers? Learning lwt	8	3579	November 23, 2017
Dune exec + dune build running in the same project (web server + melange) Ecosystem dune , melange	8	1300	November 26, 2023
Can't compile SSL 0.7.0/LWT 5.9.2 w/ dune build Ecosystem opam , build , dune	1	85	September 4, 2025
Dune exec not same as running exe (WSL 2 on Windows) Learning	3	773	March 29, 2022

App doesn't respond to Ctrl-C / SIGINT / Signals when running dune exec

Related topics