Re: [PATCH v3 09/19] unwind: Introduce sframe user space unwinding
Josh Poimboeuf <[email protected]>
| Newsgroups | org.kernel.vger.linux-toolchains,org.kernel.vger.linux-kernel,org.kernel.vger.linux-perf-users |
|---|---|
| Message-ID | <20241101193510.53xj5ybz6vyyqb37@jpoimboe> |
On Fri, Nov 01, 2024 at 12:33:07PM -0700, Josh Poimboeuf wrote: > On Fri, Nov 01, 2024 at 02:09:08PM -0500, Segher Boessenkool wrote: > > On Thu, Oct 31, 2024 at 04:03:13PM -0700, Josh Poimboeuf wrote: > > > Actually I just double checked and even the kernel's ELF loader assumes > > > that each executable has only a single text start+end address pair. > > > > Huh? What makes you think that? There can be many executable PT_LOAD > > segments in each and every binary. > > Right, but for executables (not shared libraries) the kernel seems to > assume they're contiguous? See the 'start_code' and 'end_code' > variables in load_elf_binary() load_elf_interp(). Typo, see load_elf_binary (not load_elf_interp). -- Josh