public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dberlin at dberlin dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info
Date: Tue, 28 Dec 2004 18:49:00 -0000 [thread overview]
Message-ID: <20041228184934.3092.qmail@sourceware.org> (raw)
In-Reply-To: <20041222003609.19124.hjl@lucon.org>
------- Additional Comments From dberlin at dberlin dot org 2004-12-28 18:49 -------
Subject: Re: [4.0 regression] gcc generates incorrect
dwarf2 debug info
On Tue, 2004-12-28 at 18:37 +0000, hjl at lucon dot org wrote:
> ------- Additional Comments From hjl at lucon dot org 2004-12-28 18:37 -------
> With the patch applied, gdb 6.3 still dumps core.
>
With the patch applied, we generate correct debug info for the case you
pasted.
I can do nothing more on the gcc side.
In fact, I'm seriously considering *not* applying this patch, because we
still can't guarantee that the base and end addresses won't end up
different anyway.
I'm soliciting opinions from gdb folks and the dwarf2 reflector folks as
we speak, and based on what they say, i'll either apply the patch or
close as wontfix.
In any regard, there is a gdb bug here somewhere that needs to be fixed.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19124
next prev parent reply other threads:[~2004-12-28 18:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 0:36 [Bug debug/19124] New: " hjl at lucon dot org
2004-12-22 0:53 ` [Bug debug/19124] " hjl at lucon dot org
2004-12-22 1:09 ` hjl at lucon dot org
2004-12-22 1:12 ` pinskia at gcc dot gnu dot org
2004-12-22 1:34 ` pinskia at gcc dot gnu dot org
2004-12-22 13:07 ` steven at gcc dot gnu dot org
2004-12-26 0:56 ` dberlin at gcc dot gnu dot org
2004-12-28 2:34 ` pinskia at gcc dot gnu dot org
2004-12-28 18:39 ` hjl at lucon dot org
2004-12-28 18:49 ` dberlin at dberlin dot org [this message]
2004-12-30 3:38 ` hjl at lucon dot org
2004-12-30 5:10 ` dberlin at dberlin dot org
2004-12-30 21:01 ` hjl at lucon dot org
2005-01-02 20:29 ` dberlin at gcc dot gnu dot org
2005-01-04 20:07 ` ac131313 at redhat dot com
2005-01-10 16:45 ` dberlin at dberlin dot org
2005-01-10 18:32 ` dberlin at gcc dot gnu dot org
2005-01-10 18:55 ` hjl at lucon dot org
2005-01-10 22:37 ` hjl at lucon dot org
2005-01-20 20:10 ` cvs-commit at gcc dot gnu dot org
2005-01-20 20:15 ` dberlin 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=20041228184934.3092.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).