You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's because the tracer invokes callback functions that dispatch via a global(!) var which we can only set after initialising the tracer. Chicken and egg. Easy to fix.
The text was updated successfully, but these errors were encountered:
rade
added
the
bug
Broken end user or developer functionality; not working as the developers intended it
label
Jul 6, 2017
We defer starting the ebpf tracer until we've set the global var which
is referenced by the callback functions. Previously the var could be
unset when the callbacks are invoked, resulting in a segfault.
Fixes#2687.
Apply
and then start a probe
That's because the tracer invokes callback functions that dispatch via a global(!) var which we can only set after initialising the tracer. Chicken and egg. Easy to fix.
The text was updated successfully, but these errors were encountered: