Hello, community,
I encountered an interesting problem when I use the coroot to profile the Envoy sidecar (data plane of Istio service mesh). When a stripped binary is used (most symbols are stripped but some dynamic symbols that required by other dynamic lib/modules are kept), we found the Envoy show lots of envoyGoFilterLogLevel. I check it again and again and finally ensure this method is never be called in the node.
Then, we tried to compiled the envoyGoFilterLogLevel out, we found the luaopen_jit occurs.
I guess this is an error that when the coroot cannot get the correct symbol from the binary, some unrelated symbol will be used to fill the stack.

Hello, community,
I encountered an interesting problem when I use the coroot to profile the Envoy sidecar (data plane of Istio service mesh). When a stripped binary is used (most symbols are stripped but some dynamic symbols that required by other dynamic lib/modules are kept), we found the Envoy show lots of
envoyGoFilterLogLevel. I check it again and again and finally ensure this method is never be called in the node.Then, we tried to compiled the
envoyGoFilterLogLevelout, we found theluaopen_jitoccurs.I guess this is an error that when the coroot cannot get the correct symbol from the binary, some unrelated symbol will be used to fill the stack.