public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/9457] gdb prints incorrect backtrace when on RET at end of a procedure
Date: Sat, 06 Jan 2024 19:04:33 +0000 [thread overview]
Message-ID: <bug-9457-4717-x2xVa5ay1e@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-9457-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=9457
Hannes Domani <ssbssa at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ssbssa at sourceware dot org
--- Comment #2 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to drow@false.org from comment #1)
> From: Daniel Jacobowitz <drow@false.org>
> To: p1rpp@yahoo.co.uk
> Cc: gdb-gnats@sources.redhat.com
> Subject: Re: backtrace/2352: gdb prints incorrect backtrace when on RET at
> end of a procedure
> Date: Tue, 30 Oct 2007 09:38:08 -0400
>
> On Tue, Oct 30, 2007 at 01:27:28PM -0000, p1rpp@yahoo.co.uk wrote:
> > >Synopsis: gdb prints incorrect backtrace when on RET at end of a
> procedure
>
> Unfortunately, this is a known bug in all versions of GCC.
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12990
>
> The compiler generates incorrect debug tables.
>
> --
> Daniel Jacobowitz
> CodeSourcery
Since the linked gcc bug was closed (fixed for gcc 4.5), can this be closed as
well?
--
You are receiving this mail because:
You are on the CC list for the bug.
next parent reply other threads:[~2024-01-06 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9457-4717@http.sourceware.org/bugzilla/>
2024-01-06 19:04 ` ssbssa at sourceware dot org [this message]
2024-01-10 18:31 ` 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-9457-4717-x2xVa5ay1e@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).