public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel at mariadb dot org" <sourceware-bugzilla@sourceware.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	[thread overview]
Message-ID: <bug-31349-131-6yiGPBcqcm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31349-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31349

--- Comment #2 from daniel at mariadb dot org <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 returned
by backtrace as they form part of the call stack.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-02-07  8:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07  1:04 [Bug libc/31349] New: " daniel at mariadb dot org
2024-02-07  8:43 ` [Bug libc/31349] " fweimer at redhat dot com
2024-02-07  8:58 ` daniel at mariadb dot org [this message]
2024-02-07 10:06 ` schwab@linux-m68k.org
2024-02-07 10:18 ` schwab@linux-m68k.org
2024-02-07 10:46 ` fweimer at redhat dot com
2024-02-07 10:54 ` schwab@linux-m68k.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-31349-131-6yiGPBcqcm@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).