kindling开启trace后,Java项目报错,libstdc++.so.6: 无法打开共享对象文件

[jokerZhou]

Caused by: java.lang.UnsatisfiedLinkError: /tmp/kindling/1.0.3/libasyncProfiler.so: libstdc++.so.6: 无法打开共享对象文件: 没有那个文件或目录
怎么解决啊?

[jokerZhou]

java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at io.kindling.boot.KindlingBootstrap.install(KindlingBootstrap.java:132)
at io.kindling.boot.KindlingBootstrap.agentmain(KindlingBootstrap.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:386)
at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:411)
Caused by: java.lang.UnsatisfiedLinkError: /tmp/kindling/1.0.3/libasyncProfiler.so: libstdc++.so.6: 无法打开共享对象文件: 没有那个文件或目录
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1934)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1817)
at java.lang.Runtime.load0(Runtime.java:810)
at java.lang.System.load(System.java:1086)
at io.kindling.agent.deps.one.profiler.AsyncProfiler.getInstance(AsyncProfiler.java:44)
at io.kindling.agent.profiler.Profiler.(Profiler.java:31)
at io.kindling.agent.service.AsyncProfilerService.(AsyncProfilerService.java:30)
at io.kindling.agent.service.ServiceManagerImpl.(ServiceManagerImpl.java:44)
at io.kindling.agent.KindlingAgent.premain(KindlingAgent.java:46)
... 12 more

[dxsup]

这个应用的基础镜像是alpine linux吧，目前还没有支持这个环境

[jokerZhou]

哦 好的 换个环境看看..

[dxsup]

如果出现warning日志是因为这个环境有些技术不支持，但关系不大，会自动切换到另外一种实现，后续版本会关掉这个warning