Ian,
Thankyou VERY much for your reply. Your analysis was spot-on. There is a
3rd way that a goroutine could have the stack ripped out from under it - if
it is running a signal handler. Go uses the SA_ONSTACK (alternate signal
stack) facility which we had adopted for YottaDB as well. Back when
Thanks for the reply Charles. I did look into this but did not find
anything further along these lines.
--
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-nu
generally asleep on a timer. Note I'm using Go 1.14.4 on Ubuntu 18.04.
Here is the list of goroutines from delve (which I've only just started
using so not well versed in its usage):
[3:01pm] [estess@flyingv] :
/testarea/estess/tst_V994_R129_dbg_04_200701_144712/go_0_6/sigint/go/src/
Although I spent some time searching, I have not found an issue quite like
the one I’m experiencing so here goes. We are working to create a set of
Golang wrapper functions/methods that call into an existing database
product (YottaDB) that has a C interface. This was going well until we ran
i
