> -----Original Message----- > From: > avr-gcc-list-bounces+eric.weddington=atmel....@nongnu.org > [mailto:avr-gcc-list-bounces+eric.weddington=atmel....@nongnu. > org] On Behalf Of Joerg Wunsch > Sent: Wednesday, September 01, 2010 12:26 PM > To: avr-gcc-list@nongnu.org > Subject: Re: [avr-gcc-list] AVR Studio lacks ability to > displayout-of-scopevariables? (was: Frame pointer location) > > "Weddington, Eric" <eric.wedding...@atmel.com> wrote: > > >> I was referring to automatic variables from your caller(s), i.e. > >> everything where you have to unwind the stack in order to see them. > > > Is there enough DWARF2 info in the generated ELF file to > fully support = > > this feature? > > I'm not sure about that. Remember, our DWARF-2 support is still > "accidental" (or incidental), it's only a by-product of other GCC > platforms moving to DWARF-2,
But it works, and decently. > e.g. avr-as' support of --gdwarf-2 is > disfunctional, I need to check... I thought that that might be fixed now. But I can't remember if that's upstream, or in a patch. > and AVR-GDB cannot usefully handle DWARF-2 at all. That's a completely separate issue. I just want to be sure, right now, if the required debug information is being generated in the ELF file for *any* debugger to take advantage of. Thanks, Eric _______________________________________________ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
