This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: avr-gcc, .debug_frame and bitfields
- From: Denis Chertykov <denisc at overta dot ru>
- To: Torleif Sandnes <tsandnes at atmel dot no>
- Cc: gcc at gcc dot gnu dot org
- Date: 04 May 2004 09:50:02 +0400
- Subject: Re: avr-gcc, .debug_frame and bitfields
- References: <40964170.80905@atmel.no>
Torleif Sandnes <tsandnes@atmel.no> writes:
> I have configured avr-gcc like this:
>
> bash-2.05$ avr-gcc -v
> Reading specs from /usr/local/bin/../lib/gcc/avr/3.4.0/specs
> Configured with: ./configure --prefix=/usr/local/
> --enable-languages=c,c++ --enable-version-specific-runtime-libs
> --target=avr --with-dwarf2
> Thread model: single
> gcc version 3.4.0
>
> When building objects, I am unable to make gcc output the .debug_frame section.
> This is how I build my objects:
>
> >avr-gcc -mmcu=atmega169 -gdwarf-2 -o test.elf test.c
Avr port support only stabs debugging format.
(-g equal to -gstabs.)
[...]
> DW_AT_bit_offset : 0
> DW_AT_data_member_location: 2 byte block: 23 1 (DW_OP_plus_uconst: 1)
>
> Are these problems specific for the AVR target?
Yes.
> How would I go about to fix these problems?
Rewrite code which handle debugging information.
Denis.