While inode-uprobes makes $subject probe type not trivially available, we should still be able to hack around it in the runtime. Given the requested virtual address, aat registration time we could walk the process address space, find the inode & offset corresponding to that address (if any!), and place a inode+offset uprobe there. (This doesn't help non-inode gaps in the address space, alas.)
We'll take a stab at implementing `process.statement(0xaddr)` first for inode-based uprobes, with relative addresses in the executable files (including DSO and PIE). This will pave a way to true DWARF-less probing (with the existing @vma() facility which will get merge soon) as well as implementing our own uretprobes without all the consequences from the kernel's uretprobes. Messed up C stacks are really problematic for stack unwinding and resizable stacks.