This repository has been archived by the owner on Dec 16, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 88
Segfault in Context::onResponseHeaders()
#180
Comments
Looks like sendLocalReply is the critical bit. |
What can I do to repro this? |
This is very odd as the only the only throw in std::function is for a null std::function and we test right about the call if it is null: Http::FilterHeadersStatus Context::onResponseHeaders() { |
So, without a way to repro I don't have a path forward. |
SendLocalReply is from the blackhole cluster. |
jplevyak
added a commit
to jplevyak/envoy-wasm
that referenced
this issue
Sep 13, 2019
envoyproxy#180 Signed-off-by: John Plevyak <jplevyak@gmail.com>
jplevyak
added a commit
to jplevyak/envoy
that referenced
this issue
Sep 17, 2019
…stio#189) * Fix segfault by ensuring that we have created the context in the VM. envoyproxy/envoy-wasm#180 Signed-off-by: John Plevyak <jplevyak@gmail.com>
jplevyak
added a commit
to istio/envoy
that referenced
this issue
Sep 17, 2019
…189) (#107) * Fix segfault by ensuring that we have created the context in the VM. envoyproxy/envoy-wasm#180 Signed-off-by: John Plevyak <jplevyak@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1.3.0-rc3
The text was updated successfully, but these errors were encountered: