I am using the Go libraries for GRPC.
My situation is as follows where GRPC Client2 is invoked from the same
thread as GRPC-Server1.
GRPC-Client1======[GRPC-Server1====GRPC Client2]==========GRPC-Server2
The GRPC Client2 is crashing as follows.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x76b4ec]
goroutine 41 [running]:
google.golang.org/grpc.Invoke(0x7ff5961e98c0, 0xc420070178, 0x8d9601, 0x1e,
0x88c280, 0xc42006c640, 0x8727e0, 0xc420514540, 0x0, 0x0, ...)
/root/go/src/google.golang.org/grpc/call.go:149 +0x2c
I believe my code is ok because the basic client-server GRPC works fine
when run separately.
GRPC-Client1 ==== GRPC-Server1
GRPC-Client2==== GRPC-Server2
Are there any known issues when running a GRPC client from the same thread
as a GRPC server ??
Thanks,
Farhad
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/6cb0506f-8dba-4ef6-b824-3aff7922d4bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
