I see this happening on ADT. For example, https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-hwe-5.4/20200918_130259_40c27@/log.gz.
The only way I see it happening is some header defining PTRACE_SECCOMP_GET_METADATA macro, not struct seccomp_metadata. I don't see that on linux-libc-dev headers for bionic. There is something fishy going on here.
Cascardo.
I see this happening on ADT. For example, https:/ /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- bionic/ bionic/ amd64/l/ linux-hwe- 5.4/20200918_ 130259_ 40c27@/ log.gz.
The only way I see it happening is some header defining PTRACE_ SECCOMP_ GET_METADATA macro, not struct seccomp_metadata. I don't see that on linux-libc-dev headers for bionic. There is something fishy going on here.
Cascardo.