public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ericw at evcohs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/19087] Overflowed address in dwarf debug line information
Date: Mon, 20 Dec 2004 17:44:00 -0000 [thread overview]
Message-ID: <20041220174427.10312.qmail@sourceware.org> (raw)
In-Reply-To: <20041220095410.19087.tsandnes@atmel.com>
------- Additional Comments From ericw at evcohs dot com 2004-12-20 17:44 -------
(In reply to comment #5)
> Hmm, on the mainline I get an error about dwarf2 not being supported:
> t.c:1: error: target system does not support the "dwarf-2" debug format
>
If you're talking about HEAD/4.0, then a seperate bug report needs to be filed.
The avr port needs to be able to be configured for DWARF2 debug info. (Yes, I
know that the avr port of GDB only uses stabs, but other tools use DWARF2.)
The OP is using 3.4.1.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |ericw at evcohs dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19087
next prev parent reply other threads:[~2004-12-20 17:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 9:54 [Bug c/19087] New: " tsandnes at atmel dot com
2004-12-20 12:53 ` [Bug debug/19087] " pinskia at gcc dot gnu dot org
2004-12-20 13:40 ` tsandnes at atmel dot no
2004-12-20 13:44 ` pinskia at gcc dot gnu dot org
2004-12-20 14:02 ` tsandnes at atmel dot com
2004-12-20 14:03 ` [Bug target/19087] " tsandnes at atmel dot com
2004-12-20 14:05 ` pinskia at gcc dot gnu dot org
2004-12-20 14:15 ` tsandnes at atmel dot no
2004-12-20 17:44 ` ericw at evcohs dot com [this message]
2005-02-11 23:13 ` ericw at evcohs dot com
2005-02-16 6:42 ` dwatkins at tascsystems dot com
2005-02-17 10:23 ` dwatkins at tascsystems dot com
2005-02-17 12:45 ` schlie at comcast dot net
2005-03-07 16:31 ` dwatkins at tascsystems dot com
2005-03-07 22:50 ` dwatkins at tascsystems dot com
2005-03-08 7:07 ` tsandnes at atmel dot no
2005-03-11 7:43 ` tsandnes at atmel dot com
2005-03-16 16:54 ` ericw at evcohs dot com
2005-05-06 14:12 ` bjoern dot m dot haase at web dot de
2005-05-09 7:02 ` tsandnes at norway dot atmel dot com
2005-05-30 21:40 ` bjoern dot m dot haase at web dot de
2005-05-30 21:40 ` bjoern dot m dot haase at web dot de
2005-07-27 23:39 ` giovannibajo at libero dot it
[not found] <bug-19087-9466@http.gcc.gnu.org/bugzilla/>
2005-12-28 23:01 ` eweddington at cso dot atmel dot com
2006-03-27 20:53 ` j at uriah dot heep dot sax dot de
2006-08-31 15:40 ` eweddington at cso dot atmel dot com
2006-08-31 15:41 ` eweddington at cso dot atmel dot com
2006-09-19 21:54 ` eweddington at cso dot atmel dot com
2006-09-20 0:00 ` dberlin at gcc dot gnu dot org
2006-09-20 3:38 ` eweddington at cso dot atmel dot com
2006-09-21 15:18 ` eweddington at cso dot atmel dot com
2007-01-31 17:24 ` aesok at gcc dot gnu dot org
2007-01-31 17:35 ` aesok at gcc dot gnu dot org
2007-02-13 19:00 ` eweddington at cso dot atmel dot com
2007-02-15 20:02 ` aesok at gcc dot gnu dot org
2007-02-15 20:14 ` aesok at gcc dot gnu dot org
2007-04-09 21:16 ` eweddington at cso dot atmel dot com
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=20041220174427.10312.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).