Namhyung Kim
Namhyung Kim
In the [nightly test setup](../blob/master/.github/workflows/nightly-test.yml), it runs `make test -j1` at 4am. But it fails like below. ``` 124 exception : NG NG OK NG OK NG NG OK OK...
I found flame-graph dump doesn't work well with a depth filter. For example, I played with the abc test program. ``` $ uftrace record t-abc $ uftrace replay # DURATION...
To support variables, uftrace replay (and others too, later) should display symbol name rather than memory address. Showing static symbols (in file) is easy and I extended it to save...
While compiling the source with clang, I noticed the following warning on the xray support code (in asm). ``` $ make ... ASM arch/x86_64/xray.op CC FPIC libmcount/mcount-fast.op CC FPIC arch/x86_64/mcount-dynamic.op...
I remember there were some suggestions using file size or elapsed time as a trigger point and associate (global) actions to it (But I cannot find where). For example, we...
I've noticed this on my archlinux machine. ``` $ make -j4 ASAN=1 unittest ... ================================================================= ==141840==ERROR: LeakSanitizer: detected memory leaks Direct leak of 5664 byte(s) in 12 object(s) allocated from:...
To implement entrire uftrace features, it should support (full) dynamic tracing either with compiler support or not. Specifically it'd support the following but we need to check the compiler implementations...
I think it's useful to provide timestamp information in the report so that users can replay at the given time later. For example, when some function is called a lot,...
I'm thinking of histogram functionality in the `hist` sub-command or maybe in a (Python) script. It can show various histogram based on the trace data. This is just to think...
This supports watchpoint to track global variables (and raw addresses). Only pritimitive integer types are supported for now. Larger types or struct will be ignored. The syntax is like following...