Bill Westfield <wes...@gmail.com> wrote: > well, based on my experiences so far, I was expecting an answer of > the form "that's this issue here, even though the description > doesn't sound anything alike", or "you fool! objdump was never > intended to disassemble the .init9 subsection!"
By the time objdump runs, it doesn't know anymore about any input sections, it's only got the main output sections (.text, .data, .bss). Source code must be trackable by means of linenumber debugging information in order to be included. So if that debugging information is missing, objdump won't be able to correlate the code addresses to source files. You can use avr-objdump -g to analyze stabs line number (and other debugging) information, or avr-objdump -Wl to analyze DWARF-2 line number information. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org https://lists.nongnu.org/mailman/listinfo/avr-gcc-list
