@notbobbytables@infosec.exchange
2026-07-25 19:40 UTC
I am not familiar with it, but out of curiosity I am wondering why they removed memory tagging on aarch64. The corresponding commit says that it was somehow broken: https://sourceware.org/git/?p=glibc.git;a=commit;h=70be9819b5eb7ed0050cffb45113332f96f5a55f
Does somebody have a nice link that explains the problem(s) in more detail?
Replies (1)
-
@pinskia@hachyderm.io 2026-07-25 23:52
@notbobbytables@infosec.exchange So what happens is gdb breaks. Because it overloads malloc. It is a bug in gdb and a newer gdb will not be released for a while. So it was decided to revert the glibc patch for now. And wait till the next release cycle for the glibc patch. The gdb fix went in as it does not break anything else too. I would provide a link but sourceware.org is under a huge ddos attack due to Ai bots.