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 is the only to put it out of misery. Is *that* expected although I know that custom signal handlers break cgo? Shouldnt it just panic and exit? Le jeudi 27 avril 2017 21:07:35 UTC+2, Tamás Gulácsi a écrit : > > > 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 the sqlnet.ora file. >> Here, we run all our OCI clients with: >> >> DIAG_SIGHANDLER_ENABLED=FALSE >> DIAG_ADR_ENABLED=FALSE >> DIAG_DDE_ENABLED=FALSE >> >> Regards, >> Didier. >> >>> >>> > Thanks a lot, Didier! > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
