-
-
Notifications
You must be signed in to change notification settings - Fork 213
CTRL+C signal causes go-oci8 program to crash on Linux and OS X #106
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
Comments
could you please check the stacktrace with gdb? |
I got the same problem too: fatal: morestack on g0 goroutine 0 [idle]: goroutine 1 [chan receive]: goroutine 5 [syscall]: goroutine 6 [chan receive]: goroutine 7 [select, locked to thread]: goroutine 8 [IO wait]: rax 0x17 |
I also get a similar stack trace. It would be nice to be able to gracefully exit on ctrl-c, but it looks like the processes are locked during db operations which doesn't allow the signal to be handled. |
Same issue on MacOSX: fatal: morestack on g0 goroutine 0 [idle]: goroutine 1 [IO wait]: goroutine 5 [chan receive]: goroutine 6 [chan receive]: goroutine 7 [IO wait]: rax 0x17 goroutine 0 [idle]: goroutine 1 [IO wait]: goroutine 19 [chan receive]: goroutine 20 [chan receive]: goroutine 21 [IO wait]: rax 0x17 goroutine 0 [idle]: goroutine 1 [IO wait]: goroutine 5 [chan receive]: goroutine 6 [chan receive]: goroutine 7 [IO wait]: rax 0x17 |
Not seeing any oic8 path in the stack trace. Maybe the issue is elsewhere? |
Hi, Issue is not found when I try using pq (postgres) driver. |
As far as I can see, this is related on golang/go#23360 or golang/go#25229 |
So if i upgrade to golang v1.11.2 (stable), this will solve the issue? � |
@mattn The issue owner has not commented since first opening this. Also does not seem like this is an issue with oci8. Close this? |
Please reopen this if you still have issue and it is related on go-oci8. |
Step to reproduce the issue:
1)build the test program (uploaded at https://github.com/jusongchen/oci8-test2)
set env variable GO_OCI8_CONNECT_STRING,e.g: GO_OCI8_CONNECT_STRING=scott/tiger@//hostname/oracle_service
run the programm and enter CTRL+C after the prompt
CTRL+C signal won't cause any issue before a DB operation. However, after a DB operation, it will crash the programm with message
"llegal instruction: 4" -- on Mac OS X
or "Trace/breakpoint trap" --on Ubuntu Linux.
The text was updated successfully, but these errors were encountered: