Skip to content

Unexpected behaviour of process interrupting when using chdb #24

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

Open
xantinium opened this issue Apr 8, 2025 · 1 comment
Open

Unexpected behaviour of process interrupting when using chdb #24

xantinium opened this issue Apr 8, 2025 · 1 comment
Assignees

Comments

@xantinium
Copy link

Hi there!

Encountered an issue: when using chdb-go, the process cannot terminate successfully upon receiving a stop signal. It appears that the library intercepts the signal, preventing the Go program from receiving it.

Steps to reproduce:

  1. Initialize a session from chdb-go
  2. Set up a listener for the SIGINT signal
  3. Run the application
  4. Send a stop signal (Ctrl+C)

Expected behavior: the program receives the stop signal and terminates successfully.
Actual behavior: the program hangs / the program terminates prematurely without receiving the stop signal.

Minimal repro: https://github.com/xantinium/chdb-stop-sig

@wudidapaopao
Copy link

wudidapaopao commented Apr 15, 2025

Hi @xantinium, thank you for your report. The current implementation of libchdb.so intercepts SIGINT and SIGQUIT signals by default, which can interfere with signal handling in Go programs. This behavior will be addressed in a future update to libchdb.so.
see chdb-io/chdb#321

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

No branches or pull requests

2 participants