<p>Now that fix is in progress on the kernel side, what should the action on the strace side be? I think the choices are roughly:</p>
<ol>
<li>
<p>Default to using kernel uapi headers with a test for whether they're broken (only needed on x32 and sparc32), falling back to libc ones if so. Users of a libc with time64 will have to ensure they have fixed uapi headers.</p>
</li>
<li>
<p>Default to using libc headers unless arch is 32-bit and time_t is 64-bit. In that case, fallback to kernel uapi headers.</p>
</li>
</ol>
<p>I like approach 1 better because it's semantically correct, and would also work if libc were just using different structures to interface with applications independent of anything to do with time_t. The definitions strace wants here really are the ones defining the ABI between user and kernel space, not between application and libc.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/strace/strace/issues/116?email_source=notifications&email_token=AAFX7DGIKY3D4FD7QYPB6ODQ5YWJNA5CNFSM4J63O5QKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6HB5I#issuecomment-574386421">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAFX7DC6JJEVWJBDIRJFVB3Q5YWJNANCNFSM4J63O5QA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AAFX7DB6AWNYQUEMNTJYV43Q5YWJNA5CNFSM4J63O5QKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6HB5I.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/strace/strace/issues/116?email_source=notifications\u0026email_token=AAFX7DGIKY3D4FD7QYPB6ODQ5YWJNA5CNFSM4J63O5QKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6HB5I#issuecomment-574386421",
"url": "https://github.com/strace/strace/issues/116?email_source=notifications\u0026email_token=AAFX7DGIKY3D4FD7QYPB6ODQ5YWJNA5CNFSM4J63O5QKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6HB5I#issuecomment-574386421",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>