From c94ade9e77a811d3ff75ffc2889a65375262ab1f Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Tue, 10 Nov 2026 23:55:42 -0300 Subject: trace: names for PLT stubs and GOT slots; a call followed down; the vDSO is run through For a disassembly that follows a call into libc. A stub is open@plt and a slot open@got, from the relocations (libc's own, IFUNC and nameless, by the function they resolve to); telescope.got says what a slot holds and whether it is still lazy. A library function's entry is named even when its mapping was not known yet, by the alias the program imports. The chain holds through the stub's jump, the callee's first instruction, the syscall and the loader's resolver: ld.so's unwind section lacks the entry that ends it, which lost every frame there. A syscall is tied to its instruction's moment, and each frame's call is recorded with the row before it. Stepped by instruction, a call into the vDSO is one moment and its return the next: its clock loop, single-stepped, made three million moments of three reads. Co-Authored-By: Claude Fable 5.2 Claude-Session: https://claude.ai/code/session_016Y9MNCKgYCGiANnEwcEQxa --- targets/hello.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 targets/hello.c (limited to 'targets/hello.c') diff --git a/targets/hello.c b/targets/hello.c new file mode 100644 index 0000000..b575e6f --- /dev/null +++ b/targets/hello.c @@ -0,0 +1,15 @@ +// main calls libc through the PLT, each call a system call: a call followed +// down, through the stub and libc's wrapper to the kernel, and back up. +// Linked for lazy binding: a function's first call runs the loader's +// resolver, its second (the second read) goes straight to it. +#include +#include + +int main(int argc, char **argv) { + char buf[16]; + int f = open(argv[0], O_RDONLY); + long n = read(f, buf, sizeof buf); + n += read(f, buf, sizeof buf); + close(f); + return n == 2 * sizeof buf ? 0 : 1; +} -- cgit v1.3