public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/30929] 'frame function' fails when call is the last instruction
Date: Sun, 01 Oct 2023 16:40:48 +0000	[thread overview]
Message-ID: <bug-30929-4717-KjoY5TYM0R@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30929-4717@http.sourceware.org/bugzilla/>

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2023-10-01
                 CC|                            |tromey at sourceware dot org
             Status|UNCONFIRMED                 |WAITING

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
Can you try git master gdb?
I suspect this is a dup of bug#29074.

If not, then it is probably another instance of bug#8416 -
same idea, just need to track down the spot with the incorrect call.

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

  reply	other threads:[~2023-10-01 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01 15:51 [Bug backtrace/30929] New: " amonakov at gmail dot com
2023-10-01 16:40 ` tromey at sourceware dot org [this message]
2023-10-01 17:13 ` [Bug backtrace/30929] " amonakov at gmail dot com
2023-10-06 12:33 ` tromey at sourceware dot org
2024-01-10 20:10 ` tromey at sourceware dot 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-30929-4717-KjoY5TYM0R@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).