stack: ~ probe: tp:skb:kfree_skb/stack pcap: - args: probe: tp:skb:kfree_skb Expand All@@ -16,7 +16,7 @@ collect: - args: collectors: nft,skb nft_verdicts: drop stack: ~ probe: kprobe:__nft_trace_packet/stack p
In some cases, stack traces contain a bunch of lines from third party packages, and I would prefer to omit those lines from the stack trace, as it's extremely unlikely that I need to be aware of them. Suggested solution Add an option like filterStack that takes a function that receives ...
Rest of stack: at div\n at t (https://www.geocaching.com/play/map/public/vendors~SearchMapDecorators.d587c1a4ff4bb126d6e3.js:2:250836)\n at div\n at I (https://www.geocaching.com/play/map/public/SearchMapDecorators.d76620256b95cda24019.js:1:83441)\n at ...
As an example, the collection efficiency of coarse quarts fibre filters towards Zn, Cd, Pb and Cu has been assessed during stack gas sampling from waste incinerators. The filter penetration is discussed in relation to sampling precision, and requirements in the selection of trace metal sampling ...
As an example, the collection efficiency of coarse quarts fibre filters towards Zn, Cd, Pb and Cu has been assessed during stack gas sampling from waste incinerators. The filter penetration is discussed in relation to sampling precision, and requirements in the selection of trace metal sampling ...
The trace feature is really powerful and helpful. I hope this could make it even better. For example, I'd like to exclude stack trace of node_modules dependencies like redux-thunk so that I could focus on my source code. Perhaps the UI c...