libcrypto backtrace information #8853
Description
My issue is a very language-specific, however it could reveal some internal libcrypto problems. There is a small Go application that uses OpenSSL via cgo interface: https://github.com/vitalyisaev2/pprof_cgo_issue. Basically it works as expected, but when trying to profile this application with standard Go toolchain, it crashes with segfault:
$ ./pprof_cgo_issue -profiler
2019/04/30 12:14:40 profile: cpu profiling enabled, cpu.pprof
Segmentation fault (core dumped)
$ gdb ./pprof_cgo_issue /tmp/core.d685d2a145b4.pprof_cgo_issue.1556626480.20
(gdb) bt
#0 0x00007fb47640c246 in ?? () from /lib64/libgcc_s.so.1
#1 0x00007fb47640cefd in _Unwind_Backtrace () from /lib64/libgcc_s.so.1
#2 0x00000000007322bc in cgoTraceback (parg=0xc0002dd970, parg@entry=<error reading variable: value has been optimized out>) at traceback.c:82
#3 0x00000000007364e6 in x_cgo_callers (sig=27, info=0xc0002ddaf0, context=0xc0002dd9c0, cgoTraceback=<optimized out>, cgoCallers=<optimized out>, sigtramp=0x46a2f0 <runtime.sigtramp>) at gcc_traceback.c:22
#4 <signal handler called>
#5 0x00007fb476614232 in ?? () from /lib64/libcrypto.so.1.1@ianlancetaylor from Golang community suggested that libcrypto may not have correct backtrace information. Could you please check it?