go-mruby: fatal error: exitsyscall: syscall frame is no longer valid
ref https://github.com/errordeveloper/kubeplay/issues/1
I’ve not yet been able to find what’s the simplest way to reproduce this, but I am able to hit this with my project, which you can compile like this:
go get github.com/Masterminds/glide
go get -d github.com/errordeveloper/kubeplay
cd $GOPATH/src/github.com/errordeveloper/kubeplay
$GOPATH/bin/glide up
make -C vendor/github.com/mitchellh/go-mruby libmruby.a
go install ./rubykube
go build .
Create empty kubeconfig:
kind: Config
apiVersion: v1
preferences: {}
clusters:
- cluster:
server: https://localhost:8443
name: test
contexts:
- context:
cluster: test
user: test
name: test
current-context: test
users:
- name: test
user: {}
Start kubeplay and call pods []:
> ./kubeplay -kubeconfig ./kubeconfig
kubeplay (namespace="*")> pods []
+++ Execute: pods
args=[]
fatal error: exitsyscall: syscall frame is no longer valid
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 18
Commits related to this issue
- Use @erikh's patched version of go-mruby (fix #1, ref mitchellh/go-mruby/issues/49) — committed to errordeveloper/kubeplay by errordeveloper 7 years ago
ok, great information. I’ll keep trying to find the right fix, thanks.
On Sat, Jan 7, 2017 at 10:00 AM, Ilya Dmitrichenko <notifications@github.com