diff options
author | Andrei Vagin <avagin@google.com> | 2020-02-28 11:23:00 -0800 |
---|---|---|
committer | gVisor bot <gvisor-bot@google.com> | 2020-02-28 11:24:11 -0800 |
commit | 322dbfe06bfc3949b7b3a7e7add695c41213ddec (patch) | |
tree | 369dddb077fb2c17f15b9ea3b4a3c31e6b7a34b4 /pkg/bpf | |
parent | 6b4d36e3253238dd72d0861ac1220d147e1de8dd (diff) |
Allow to specify a separate log for GO's runtime messages
GO's runtime calls the write system call twice to print "panic:"
and "the reason of this panic", so here is a race window when
other threads can print something to the log and we will see
something like this:
panic: log messages from another thread
The reason of the panic.
This confuses the syzkaller blacklist and dedup detection.
It also makes the logs generally difficult to read. e.g.,
data races often have one side of the race, followed by
a large "diagnosis" dump, finally followed by the other
side of the race.
PiperOrigin-RevId: 297887895
Diffstat (limited to 'pkg/bpf')
0 files changed, 0 insertions, 0 deletions