Jaeger native tracing example segfaults

[phlax]

description

While testing the examples in the repo, i noticed that the jaeger-native-tracing example segfaults when you make an http request of it.

steps to reproduce

Follow the example instructions, eg

cd examples/jaeger-native-tracing
docker-compose up --build -d
curl -v localhost:8000/trace/1

logs

the logs from the failing container show

front-envoy_1  | [2020-07-24 12:51:35.638][11][info][config] [source/server/listener_manager_impl.cc:844] all dependencies initialized. starting workers
front-envoy_1  | [2020-07-24 12:51:35.639][11][warning][main] [source/server/server.cc:549] there is no configured limit to the number of allowed active connections. Set a limit via the runtime key overload.global_downstream_max_connections
front-envoy_1  | [2020-07-24 12:52:15.762][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:104] Caught Segmentation fault, suspect faulting address 0x10
front-envoy_1  | [2020-07-24 12:52:15.762][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers):
front-envoy_1  | [2020-07-24 12:52:15.762][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:92] Envoy version: f20c9168aa2e92b2c5b6f8103d792e66fd813c62/1.16.0-dev/Clean/RELEASE/BoringSSL
front-envoy_1  | [2020-07-24 12:52:15.763][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #0: __restore_rt [0x7f92319d18a0]
front-envoy_1  | [2020-07-24 12:52:15.765][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #1: jaegertracing::propagation::Propagator<>::extract() [0x7f922f1b4ffe]
front-envoy_1  | [2020-07-24 12:52:15.766][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #2: jaegertracing::Tracer::Extract() [0x7f922f1b531a]
front-envoy_1  | ActiveStream 0x55ca59282880, stream_id_: 12345331179989539751, state_.has_continue_headers_: 0, state_.is_head_request_: 0, state_.decoding_headers_only_: 0, state_.encoding_headers_only_: 0
front-envoy_1  | request_headers_: 
front-envoy_1  |   ':authority', 'localhost:8000'
front-envoy_1  |   ':path', '/trace/1'
front-envoy_1  |   ':method', 'GET'
front-envoy_1  |   'user-agent', 'curl/7.68.0'
front-envoy_1  |   'accept', '*/*'
front-envoy_1  |   'x-forwarded-for', '192.168.128.1'
front-envoy_1  |   'x-forwarded-proto', 'http'
front-envoy_1  |   'x-envoy-internal', 'true'
front-envoy_1  |   'x-request-id', 'efe080d2-f7ab-9e33-aabd-a460fa4164b2'
front-envoy_1  | request_trailers_: null
front-envoy_1  | response_headers_: null
front-envoy_1  | response_trailers_: null
front-envoy_1  | &stream_info_: 
front-envoy_1  |   StreamInfoImpl 0x55ca592829c8, protocol_: 1, response_code_: null, response_code_details_: null, health_check_request_: 0, route_name_: 
front-envoy_1  | /start-front.sh: line 3:    11 Segmentation fault      (core dumped) /usr/local/bin/envoy -c /etc/front-envoy.yaml --service-cluster front-proxy

[lizan]

This is known issue because of incompatible C++ ABI:
#11382 (comment)