News for hackers. Stuff that matters.

A comment on Debugging memory corruption: who the hell writes "2" into my stack?. Parent comment

Re:Debugging memory corruption: who the hell writes "2" into... by saagarjha on Tuesday December 31, 2024 @07:59AM (#42558433)
Hardware breakpoints don't work if the kernel is doing the writes, because the kernel won't let you enable them globally so they trigger outside of your program.
[ Parent | on HN ]
Re:Debugging memory corruption: who the hell writes "2" into... by mgaunard on Saturday January 04, 2025 @03:45AM (#42593459)
If you use a decent kernel like Linux, there is an API to do that from userspace without requiring you to reboot your kernel under a debugger.
[ Parent | on HN ]
Re:Debugging memory corruption: who the hell writes "2" into... by saagarjha on Saturday January 04, 2025 @04:13AM (#42593610)
I don't think I'm familiar with that API. What is it?
[ Parent | on HN ]
Re:Debugging memory corruption: who the hell writes "2" into... by mgaunard on Saturday January 04, 2025 @04:58AM (#42593786)
It's part of perf_event, available since 2.6.33.
[ Parent | on HN ]