Another attempt to address the tracepoint ABI problem [LWN.net]

Another attempt to address the tracepoint ABI problem

Posted Oct 31, 2017 15:39 UTC (Tue) by jikos (subscriber, #43140)
In reply to: Another attempt to address the tracepoint ABI problem by SelaLWN
Parent article: Another attempt to address the tracepoint ABI problem

BTW how does that tool access the function parameters? Does it assume that x86_64 ABI is always being followed, or do you require DWARF2 debuginfo data for those?

to post comments

Another attempt to address the tracepoint ABI problem

Posted Nov 1, 2017 14:33 UTC (Wed) by SelaLWN (guest, #118519) [Link] (1 responses)

It's ABI-sensitive, but if a language or runtime decides to pass arguments in a heap location or something that's not the standard ABI, it won't work (i.e. debuginfo isn't used).

Another attempt to address the tracepoint ABI problem

Posted Nov 1, 2017 16:25 UTC (Wed) by jikos (subscriber, #43140) [Link]

That makes is super-fragile though. GCC does a lot of optimizations on static functions that break x86 ABI (IPA-RA for example).