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
On Thu, Jul 2, 2020 at 2:18 PM wrote:
>
> We have developed a Go API (which we call a Go wrapper -
> https://pkg.go.dev/lang.yottadb.com/go/yottadb?tab=doc) to the YottaDB
> hierarchical key-value database (https://yottadb.com). It works well for the
> most part, but there are some edge cases
We have developed a Go API (which we call a Go wrapper -
https://pkg.go.dev/lang.yottadb.com/go/yottadb?tab=doc) to the YottaDB
hierarchical key-value database (https://yottadb.com). It works well for
the most part, but there are some edge cases during process shutdown that
are standing
