Page MenuHomeFreeBSD

linux: Make PTRACE_GETREGSET return proper buffer size
ClosedPublic

Authored by trasz on Oct 23 2021, 7:32 PM.
Tags
None
Referenced Files
Unknown Object (File)
Jan 21 2025, 11:27 PM
Unknown Object (File)
Jan 15 2025, 9:01 PM
Unknown Object (File)
Jan 13 2025, 12:21 AM
Unknown Object (File)
Dec 26 2024, 2:32 AM
Unknown Object (File)
Dec 26 2024, 2:15 AM
Unknown Object (File)
Dec 25 2024, 2:49 PM
Unknown Object (File)
Dec 10 2024, 3:04 AM
Unknown Object (File)
Dec 9 2024, 2:34 AM
Subscribers

Details

Summary

This fixes Chrome warning:

[1022/152319.328632:ERROR:ptracer.cc(476)] Unexpected registers size 0 != 216, 68

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

trasz requested review of this revision.Oct 23 2021, 7:32 PM
trasz retitled this revision from linux: Make PTRACE_GETREGSET return proper buffer size to linux: Make PTRACE_GETREGS return proper buffer size.Oct 29 2021, 12:24 PM

Was this just an incorrect understanding in R10:faf2fa21d70b1e625cb7af032e6608e631931486?

That one's for PTRACE_GETREGSET, while this revision changes PTRACE_GETREGS - although it incorrectly claimed to do PTRACE_GETREGSET; fixed now :-)

I think it was just a misunderstanding in d82de05480f; strace(1) seems to accept the previous, truncated, struct somehow.

This revision is now accepted and ready to land.Oct 29 2021, 1:34 PM

Sigh, no, you were right. My comment is for https://reviews.freebsd.org/D32601, not for this one here.

trasz retitled this revision from linux: Make PTRACE_GETREGS return proper buffer size to linux: Make PTRACE_GETREGSET return proper buffer size.Oct 29 2021, 2:31 PM