Honggyu Kim
Honggyu Kim
I'm okay with it. We should also think how to handle the case when `-H` option is used.
@junhoryu Thanks! Please take it and let me know if you have any problems.
@junhoryu Do you still have a plan to work on this?
It seems the `ARGBUF_SIZE 1024` is not enough for this rust program recording at https://github.com/namhyung/uftrace/blob/04d73dc31cafef4161321e3c2443a5490ef93018/libmcount/internal.h#L80. I don't see the warning messages after changing this to `2048` as follows. ```diff diff...
In addition, I also see many `invalid stack offset` messages in verbose mode. ``` $ uftrace record -P. -a --no-libcall -v ./gluesql-cli uftrace: running uftrace v0.14-14-g1365 ( x86_64 dwarf python3...
@MichelleJin12 Thanks for the testing. We may have to think about just increasing buffer size is enough. @namhyung Is it possible to manage the argument buffer dynamically?
For example, a simple hello world program shows the following trace output. ``` $ sudo uftrace -k hello Hello World! # DURATION TID FUNCTION 0.295 us [ 8854] | __monstartup();...
> I think doing make clean need enlarged. Could you explain what you mean by enlarged? Do you mean your problem is fixed by just running `make clean`?
Maybe we can provide an option something like `--kernel-verbosity` but it might be not easy to categorize which functions are verbose functions and which are not.
It's related to #1756.