Viktor Malík
Viktor Malík
Hi @netoptimizer, thanks for the report! Indeed, we do not handle bools in tracepoints correctly. I put up #3436 to fix that, would you have a chance to give it...
@ajor I was able to repro on my kernel. Tried 0.21 and it suffers from the same issue. Haven't got a chance to try older bpftrace versions but I'll give...
There's the JSON output (`-f json`) which can be further processed through some pretty-printer (e.g. `jq`). Unfortunately, it seems to have issues for this particular case (JSON doesn't support hex...
I spoke about this with @jordalgo today and I think that we should gate this behind the `--unsafe` flag. My reasoning is that bpftrace is an *observability* tool so it...
My thoughts w.r.t. this: - In the sake of reliability, displaying these warnings is useful as if they are missed, the script may silently return wrong information. So, we should...
This looks like a useful feature. I think that it would be limited to the `print` builtinl, right? Anyways, it should be quite easy to add a new config option...
Just a couple of thoughts on what was said in this thread: > what if we introduced named arguments I like the idea. Also, it would make it easier to...
> Bear in mind that there are already ways to print integers as hex in the given use-cases, they just take a bit more manual work with `printf` (a function...
@historicattle sure! I just assigned the issue to you.
I like this, it could lift some pressure of making these big features future-proof and backwards-compatible from the very beginning. I'm not sure how it would work for some features,...