Dmitrii Kuvaiskii

@woju Is this meta-issue still relevant? What are the unfinished items? Can we close this issue?

@gus6202 Could you check this discussion: https://github.com/gramineproject/gramine/issues/361 ? It provides some explanations on what could be done with gRPC. Hopefully it helps.

Jenkins, retest Jenkins-Debug-18.04 please (`LibOS.shim.test.ltp.test_ltp.test_ltp[fcntl14_64]` and `LibOS.shim.test.ltp.test_ltp.test_ltp[fdatasync01]` timed out, unrelated)

Closed in favor of https://github.com/gramineproject/gramine/pull/877 (rebased and improved version)

@M-V-Manikandan Could you edit your logs as code snippets (use "Insert Code" button or just use triple backticks)?

Please post the Gramine log with `loader.log_level = "all"`. This will print out much more information. Currently I don't see anything helpful in the Gramine log.

@M-V-Manikandan In your attached log, I still see some failures of memory allocation: ``` [P1:T6:sqvs] trace: ---- shim_mmap(0, 0x8000000, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0x0) ... [P1:T6:sqvs] trace: ---- return from shim_mmap(...)...

@M-V-Manikandan There is some more output from the Go application itself, based on your log: ``` goroutine [running]: flag.init(): /usr/local/go/src/flag/flag.go:1010+0x176 ``` If I understand correctly, there is something wrong on...

@M-V-Manikandan Disable the Gramine log (set `loader.log_level = "error"`) and look at what Go app writes to you. Go app actually gives you a lot of information about the error....

Thanks for the log! Golang prints very good backtraces. Now we see that Golang has issues in the polling mechanism (epoll, see https://man7.org/linux/man-pages/man7/epoll.7.html): ``` runtime: netpollBreak write failed with 13...