public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tsandnes at atmel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/17994] New: avr-gcc does not output a dwarf2 .debug_frame section
Date: Thu, 14 Oct 2004 08:22:00 -0000 [thread overview]
Message-ID: <20041014082220.17994.tsandnes@atmel.com> (raw)
avr-gcc-v:
Reading specs from c:/programs/WinAVR/bin/../lib/gcc/avr/3.4.1/specs
Configured with: ../gcc-3.4.1/configure --prefix=e:/avrdev/install
--build=mingw32 --host=mingw32 --target=avr --enable-languages=c,c++
Thread model: single
gcc version 3.4.1
command line:
avr-gcc -gdwarf-2 anycode.c -o anyobject.elf
No matter how I tweak the command line parameters to avr-gcc I am unable to make
it output dwarf2 callstack information (.debug_frame). I have confirmed that
this is a missing feature for the AVR port.
--
Summary: avr-gcc does not output a dwarf2 .debug_frame section
Product: gcc
Version: 3.4.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: debug
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: tsandnes at atmel dot com
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: 386
GCC target triplet: AVR
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17994
next reply other threads:[~2004-10-14 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 8:22 tsandnes at atmel dot com [this message]
2004-10-14 13:24 ` [Bug target/17994] " pinskia at gcc dot gnu dot org
2004-10-14 13:24 ` pinskia at gcc dot gnu dot org
2004-10-14 16:39 ` ericw at evcohs dot com
2004-11-13 16:17 ` berndtrog at yahoo dot com
2005-02-11 23:09 ` ericw at evcohs dot com
2005-03-16 16:54 ` ericw at evcohs dot com
2005-05-06 13:59 ` bjoern dot m dot haase at web dot de
2005-07-27 23:37 ` giovannibajo at libero dot it
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=20041014082220.17994.tsandnes@atmel.com \
--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).