public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/24490] [4.1 Regression] gcc / gdb backtrace problem
Date: Wed, 02 Nov 2005 00:00:00 -0000	[thread overview]
Message-ID: <20051102000028.4244.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24490-11423@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from pinskia at gcc dot gnu dot org  2005-11-02 00:00 -------
(In reply to comment #7)
> I've just had a look at gdb PR 2024 and disagree with the comment "backtrace
> fails when function ends with call to abort". The following code also ehibits
> the problem noted here.
Well by the time we get to expand to RTL, the rest of the function has already
deleted from the CFG as there is no way to get to the code (as it is
unreachable code).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24490


  parent reply	other threads:[~2005-11-02  0:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-23  4:08 [Bug c/24490] New: " kev dot gilbert at cdu dot edu dot au
2005-10-23 14:12 ` [Bug debug/24490] " pinskia at gcc dot gnu dot org
2005-10-23 14:34 ` [Bug debug/24490] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-10-23 22:13 ` kev dot gilbert at cdu dot edu dot au
2005-10-31  6:40 ` mmitchel at gcc dot gnu dot org
2005-11-01  2:45 ` wilson at gcc dot gnu dot org
2005-11-01 23:22 ` wilson at gcc dot gnu dot org
2005-11-01 23:55 ` kev dot gilbert at cdu dot edu dot au
2005-11-02  0:00 ` pinskia at gcc dot gnu dot org [this message]
2005-11-14 21:09 ` wilson at gcc dot gnu 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=20051102000028.4244.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).