Support MemorySanitizer origin tracking [234049217]

Feature Request

Status Update

No update yet.

Description

ni...@google.com

created issue #1

May 26, 2022 08:30PM

MemorySanitizer instrumentation for Reactor's JIT-compiled routines was implemented as part of b/155148722, but origin tracking was not implemented. For builds compiled with -fsanitize-memory-track-origins this can cause confusing error reports, both because there is no propagation of the origins for variables/memory on the C++ side which causes errors in the JIT code, and for variables part of the JIT code itself.

It should be straightforward to enable origin tracking for the former cases. For the latter, SPIR-V debug information or just numerical IDs could be used for the SPIR-V variables.

Comments

ap...@google.com <ap...@google.com> #2May 27, 2022 02:32PM

Hi Boris,

I'm Kevin from the Google Analytics API Team.

Currently, the measurement protocol doesn't support passing IP parameter. Also, our documentation states that "While it is possible to send events to Google Analytics solely with measurement protocol, only partial reporting may be available. The purpose of measurement protocol is to augment existing events collected via gtag, GTM, or Firebase.". You may try implementing custom dimensions to track unsupported values in measurement protocol.

Regards,

Kevin Soriano, Google Analytics API Team

Issue 234049217

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2May 27, 2022 02:32PM

Add comment

Issue metadata