May 12, 2021 5:15 PM, "Samuel Thibault" wrote:
> Sergey Bugaev, le jeu. 13 mai 2021 00:12:14 +0300, a ecrit:
>
>> On Wed, May 12, 2021 at 11:48 PM Samuel Thibault
>> wrote:
>>> * Symbolicated flags and file paths (potentially, also proc and auth
>>> handles)
>>
>
>> P. S. Could you please ta
Sergey Bugaev, le jeu. 13 mai 2021 00:12:14 +0300, a ecrit:
> On Wed, May 12, 2021 at 11:48 PM Samuel Thibault
> wrote:
> > > * Symbolicated flags and file paths (potentially, also proc and auth
> > > handles)
> >
> > For file path it'll probably be much harder since there can be several
> > path
On Wed, May 12, 2021 at 11:48 PM Samuel Thibault
wrote:
> > * Symbolicated flags and file paths (potentially, also proc and auth
> > handles)
>
> For file path it'll probably be much harder since there can be several
> path (or even no path!) for a given file port.
And as far as I can see, there
Hello,
Sergey Bugaev, le mer. 12 mai 2021 20:37:55 +0300, a ecrit:
> 111<--144(pid1004)->dir_lookup ("proc/loadavg" 1 0) = 0 1 "loadavg"
> 163<--162(pid1004)
> task133(pid1004)->mach_port_mod_refs (pn{ 21} 0 1) = 0
> 163<--162(pid1004)->dir_lookup ("loadavg" 1 0) = 0 1 ""
> 165<--158(pi
Hello,
I use rpctrace a lot, but I'm not particularly fond of its output
format. Other tracing tools, like strace [0] on Linux and Darling's
xtrace [1] can symbolicate many flags and structures, producing
something that looks much closer to C code, and comprehensible at a
glance.
[0]: https://str
