Displaying 3 results from an estimated 3 matches for "xray_basic_logging".
2018 Jun 28
2
XRay feature – pid reporting
...ared up my confusion about version numbers.
> >
> > I've implemented the handlers and done up to 6) below. I'm unsure of how
> to test what I have added.
> >
> > 1) Update the Header.Version = 3 (from 2)
> > 2) Add a new XRayRecord for pid (XRayPidRecord) in xray_basic_logging.h
> > 3) Implement InMemoryRawLogWithPid similar to how InMemoryRawLogWithArg
> is implemented
> > 4) Implement __xray_set_handler_pid
> > 5) call __xray_set_handler_pid, passing in basicLoggingHandlePid in the
> initialization function for basic mode
> > 6) Add an ass...
2018 Jun 25
4
XRay feature – pid reporting
I would be happy to help. Could you send me the example patch? Where would
I submit my patch to be reviewed?
Thanks,
Henry
On Mon, Jun 11, 2018 at 8:31 PM, Dean Michael Berris <dean.berris at gmail.com>
wrote:
>
>
> > On 12 Jun 2018, at 07:49, Henry Zhu via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
> >
> > Hello,
> >
> >
> > I’ve
2018 Jun 07
2
XRay TID mismatch when forking
Hello,
There seems to be a bug with the value of the thread ID (TID) that is
generated by XRay when calling fork(). The value of the TID of the child
has the same TID as its parent (this is seen in the “thread: “ field of the
YAML output produced by the llvm-xray tool). This is a problem as the trace
generated contains the same TID for the parent and children processes,
making it difficult to