From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C40913858407; Wed, 7 Feb 2024 08:58:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C40913858407 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1707296318; bh=7UGIWm4FXnf0oN5Pn8jpUZVn1SoVrnaUvevJYRsIxxs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=fVDsRv2nJlwFhDdG3VFVHqcCaFRSn2B0PbuG+wTRlp6Q0nBoeHzJpUd26bqF0fMoW h2SI7oeE9ic0WwktBLuJL7O5OCUsiGaUCFNzokmDYiBdYJvF8pQsVUNpeOM3jxxChn keXlAZ7H7RtIntyQvsD5FvmRmdIV9434zr8Qnj/U= From: "daniel at mariadb dot org" To: glibc-bugs@sourceware.org Subject: [Bug libc/31349] backtrace fails to look beyond null pointer when resolving stack (x86_64) Date: Wed, 07 Feb 2024 08:58:37 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.38 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: daniel at mariadb dot org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31349 --- Comment #2 from daniel at mariadb dot org -= -- Right, so the gdb has it intercepted before the signal hander. The backtrace has the signal handler address and I assume jump point in libc reflecting the signal hander invokation by the kernel(?). But yes, I would expect the 0x00000 and dummy_function in the frames return= ed by backtrace as they form part of the call stack. --=20 You are receiving this mail because: You are on the CC list for the bug.=