You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it seems we can't properly handle binaries built with Bazel.
Here is an example log from a client using the auto instrumentation on such a binary:
{"level":"info","ts":1729185294.8680952,"logger":"Instrumentation","caller":"[email protected]/instrumentation.go:150","msg":"target process analysis completed","pid":1553249,"go_version":"1.20.11","dependencies":{"std":"1.20.11"},"total_functions_found":13}
It seems we only managed to extract the Go version, without all the dependencies and their versions.
To parse the dependencies data we use buildinfo.Read. From the documentation for that function:
// Read returns build information embedded in a Go binary file
// accessed through the given ReaderAt. Most information is only available for
// binaries built with module support.
according to that comment - I guess the reason is the binary is "not built with module support".
The text was updated successfully, but these errors were encountered:
Currently, it seems we can't properly handle binaries built with Bazel.
Here is an example log from a client using the auto instrumentation on such a binary:
It seems we only managed to extract the Go version, without all the dependencies and their versions.
To parse the dependencies data we use buildinfo.Read. From the documentation for that function:
according to that comment - I guess the reason is the binary is "not built with module support".
The text was updated successfully, but these errors were encountered: