[go-nuts] Re: Oracle db and panics on interrupt

2017-04-27 Thread pierre . curto
Hello, Thanks a lot indeed, I did not know about those. I still get crashes on OSX besides the variables being read by the OCI libs (traces shows they are). The other thing is that when this happens, the process goes into an infinite loop spitting "fatal: morestack on g0" for ever, and kill -9

[go-nuts] Re: Oracle db and panics on interrupt

2017-04-27 Thread Tamás Gulácsi
2017. április 27., csütörtök 18:18:19 UTC+2 időpontban Didier Spezia a következőt írta: > > > I'm not sure it can help with the problem, but starting with Oracle 11, > OCI installs some custom signal handlers (even catching segmentation > faults). > They can be deactivated by setting options in

[go-nuts] Re: Oracle db and panics on interrupt

2017-04-27 Thread Didier Spezia
I'm not sure it can help with the problem, but starting with Oracle 11, OCI installs some custom signal handlers (even catching segmentation faults). They can be deactivated by setting options in the sqlnet.ora file. Here, we run all our OCI clients with: DIAG_SIGHANDLER_ENABLED=FALSE DIAG_ADR_E

[go-nuts] Re: Oracle db and panics on interrupt

2017-04-26 Thread Tamás Gulácsi
2017. április 26., szerda 20:33:13 UTC+2 időpontban Pierre Curto a következőt írta: > > Hello, > > I am unsure where to log the following issue: > whenever I send an interrupt signal to a go process running an Oracle > query, it panics with either "fatal: morestack on g0" or "fatal error: > runt