This problem does not occur, when manually using ld.lld,
It does occur with xc32-ld.
Neither does it occur when building the file using clang:
clang -c -target mipsel-unknown -mno-abicalls -gdwarf-2 simple_main.c
/opt/microchip/xc32/v4.50/bin/xc32-ld simple_main.o
Mixing a file built with clang and GCC, results only in the file built with GCC
exhibiting this behaviour (while investigating in GDB).
(Linking them together with xc32-ld)
Stripping the ".debug_aranges" section, allows for proper display:
/opt/microchip/xc32/v4.50/bin/xc32-objcopy --remove-section .debug_aranges simple_main.o simple_main_trunc.o
This problem does not occur, when manually using ld.lld,
It does occur with xc32-ld.
Neither does it occur when building the file using clang: xc32/v4. 50/bin/ xc32-ld simple_main.o
clang -c -target mipsel-unknown -mno-abicalls -gdwarf-2 simple_main.c
/opt/microchip/
Mixing a file built with clang and GCC, results only in the file built with GCC
exhibiting this behaviour (while investigating in GDB).
(Linking them together with xc32-ld)
Stripping the ".debug_aranges" section, allows for proper display: xc32/v4. 50/bin/ xc32-objcopy --remove-section .debug_aranges simple_main.o simple_main_trunc.o
/opt/microchip/