Log syscalls that are handled in the shim#2646
Conversation
5183ec1 to
14a953b
Compare
|
I think the failed tests are because I'm calling Edit: I just formatted to a temporary buffer in C and called Edit 2: The goland preemption test was timing out because it makes a lot of syscalls in a busy loop. Edit 3: @sporksmith Since the shim's vdso just makes the syscall, this patch will log vdso time calls as syscalls. I think this doesn't hurt at all, but wanted to mention it here in case you think we shouldn't log these vdso calls in the strace log. The normal strace tool wouldn't log these, but we don't need to follow the strace tool. |
889a020 to
9321500
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2646 +/- ##
=======================================
Coverage ? 67.34%
=======================================
Files ? 202
Lines ? 29920
Branches ? 5827
=======================================
Hits ? 20150
Misses ? 5180
Partials ? 4590
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
9321500 to
3514604
Compare
e3874d5 to
9457701
Compare
Yeah, I think logging them is probably what we want. |
6a699c0 to
09f2155
Compare
Examples of shim-handled syscalls:
Examples of native syscalls:
The time isn't formatted properly in these log lines, but I'll leave that for a future PR.