Bug#767756: glibc: Consider providing a libc build compiled with -fno-omit-frame-pointer to help with profiling
- To: Aurelien Jarno <aurelien@aurel32.net>, 767756@bugs.debian.org
- Cc: notafile <debbugs@notafile.com>
- Subject: Bug#767756: glibc: Consider providing a libc build compiled with -fno-omit-frame-pointer to help with profiling
- From: Philipp Kern <pkern@debian.org>
- Date: Thu, 3 Apr 2025 15:39:55 +0000
- Message-id: <Z+6ryywKTuR/xH/9@master.debian.org>
- Reply-to: Philipp Kern <pkern@debian.org>, 767756@bugs.debian.org
- In-reply-to: <20200216130605.GD3034@aurel32.net>
- References: <20141102130847.28817.43507.reportbug@alap3.anarazel.de> <16a0cc98-c982-40ba-98bf-982601a941f3@www.fastmail.com> <20141102130847.28817.43507.reportbug@alap3.anarazel.de> <20200216130605.GD3034@aurel32.net> <20141102130847.28817.43507.reportbug@alap3.anarazel.de>
On Sun, Feb 16, 2020 at 02:06:05PM +0100, Aurelien Jarno wrote:
> On 2020-02-16 03:32, notafile wrote:
> > I've been running into this myself a lot lately and wonder if anything has happened regarding this since 2014, after all it's been six years.
> > I'm surprised so few people seem to be taking interest in this considering the amount of tools that rely on frame pointers for performant stack traces, which has further increased with the introduction of eBPF.
> I understand the need for -fno-omit-frame-pointer, however it has a
> performance impact, so we do not want to do that by default. OTOH
> providing an alternative libc is something tricky if we do not want it
> to do it without breaking systems. Someone has to come with a patch that
> is well tested.
Would it be worth to consider -fno-omit-frame-pointer together with
-momit-leaf-frame-pointer?
Kind regards
Philipp Kern
Reply to: