public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rearnsha@gcc.gnu.org
To: a.bocaniciu@computer.org, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: debug/7032: arm-elf-gcc 3.1 generates wrong DWARF-2, unlike 3.0.4
Date: Mon, 30 Sep 2002 06:42:00 -0000 [thread overview]
Message-ID: <20020930134233.2681.qmail@sources.redhat.com> (raw)
Synopsis: arm-elf-gcc 3.1 generates wrong DWARF-2, unlike 3.0.4
State-Changed-From-To: open->feedback
State-Changed-By: rearnsha
State-Changed-When: Mon Sep 30 06:42:30 2002
State-Changed-Why:
This sounds more like a bug in AXD than in gcc. GCC is designed to work with GDB as the primary consumer of the debug information. If you want this problem to be fixed then you will have to supply details of precisely what debug information is causing the problem. Remember that most gcc developers don't have access to AXD.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7032
next reply other threads:[~2002-09-30 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 6:42 rearnsha [this message]
2002-10-02 9:16 Adrian Bocaniciu
2003-01-31 16:28 rearnsha
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=20020930134233.2681.qmail@sources.redhat.com \
--to=rearnsha@gcc.gnu.org \
--cc=a.bocaniciu@computer.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).