4 ms·

is your concern that some code in the process has clobbered the data that lives before the top of the stack?

• amluto 3y ago
  If you can find the top of the stack, you can read the contents with reasonable reliability. But the top of the stack is not at a fixed address, and if you are writing low enough level code (container manager, init, etc), poking around in /proc at startup is not a great idea. If you’re wiring a real runtime library, none of this matters: the kernel passes a pointer in a register at startup.
  • ithkuil 3y ago
    Do whatever libc's getauxval does to find the aux vector. Then env array is just below it, and the argv is below that iirc. EDIT: I agree it's ugly, I'm just not sure if is fair to call it brittle
    • amluto 3y ago
      The “whatever” is that glibc is the implementation of the ELF entry point. It remembers where the data structure is.