4 ms·
To all the commenters lamenting the lack of filtering capabilities, I would like to remind that this is a console program, which in the spirit of Unix should "d
by etatoby 10y ago
To all the commenters lamenting the lack of filtering capabilities, I would like to remind that this is a console program, which in the spirit of Unix should "do one thing and do it well."
If you need filtering, sorting, correlating, and so on, you should add pipes after this program. I believe Powershell pipes are even more powerful than plain text ones, although I haven't used them myself.
- MichaelMoser123 10y agostrace is a command line tool and it has the -e option to specify what calls should be displayed.
- nailer 10y agoLooks like the output is flat text, so powershell pipes: wtrace mspaint | where {$_.syscall -eq "FileIO/Close" } Don't yet work. I've made a humble feature request (https://github.com/lowleveldesign/wtrace/issues/1 https://github.com/lowleveldesign/wtrace/issues/1) if anyone is interested. Filtering by time or file, JSON/csv output and all the other powershell goodness would be awesome for a tool like this.
- xorblurb 10y agoThat's why grep is great.
- eriknstr 10y agogrep's good for sure but the comment you are replying to is a reply in turn to someone speaking specifically about powershell piping capabilities. personally i am a unix person, not a windows person, but i believe that for a tool to be most effective it should adhere to the workflow of the platform it is written for. since wtrace is written for windows it makes sense to expect that it should integrate well with the windows way of doing things.
- dekhn 10y agoThe reason the filtering needs to be in the tool, not the shell, is performance. strace hooks into every syscall made by the application, and it generates a bunch of IO, which affects the performance of the traced application badly.