Re: [avr-gcc-list] gdb: No debugging symbols found for '128 bootloader

[Kyle Jamieson]

Thanks for the response. 

> It's better if you let avr-gcc call the linker. If you want to relocate 
> your code because of a bootloader, you can do that with avr-gcc. For 
> example (ignore wrapping):
> 
> avr-gcc -mmcu=atmega128 -I. -g inpispm2.o --output inpispm2.elf -Wl,-
> Map=inpispm2.map,--cref,-Ttext=0x1E000 

I tried this, having to disable avr-gcc from trying to include libc in
the link, and my command line was:

avr-gcc -v -nostdlib -mmcu=atmega128 -I. -g inpisp.c -o inpispm2 
-Wl,-mavr5,-Ttext=0x1f800,-v,--verbose,--section-start=.bootloader=0x1e000,--cref,-T
 bootloader.lds

The result was the same:

(no debugging symbols found)...
Connection opened by host 127.0.0.1, port 32835.
0x00000000 in ?? ()
(gdb) quit