Package Details: msp430-elf-gcc 13.1.0-1

Git Clone URL: https://aur.archlinux.org/msp430-elf-gcc.git (read-only, click to copy)
Package Base: msp430-elf-gcc
Description: The GNU Compiler Collection for the msp430-elf target.
Upstream URL: http://gcc.gnu.org
Licenses: GPL, LGPL
Conflicts: msp430-elf-gcc-stage1
Provides: msp430-elf-gcc-stage1
Replaces: msp430-elf-gcc-stage1
Submitter: vonPalitroque
Maintainer: vonPalitroque
Last Packager: vonPalitroque
Votes: 14
Popularity: 0.060340
First Submitted: 2015-09-19 18:38 (UTC)
Last Updated: 2023-07-25 00:33 (UTC)

Latest Comments

« First ‹ Previous 1 2 3

vonPalitroque commented on 2015-09-28 13:43 (UTC)

Greetings, Thank you for the report. I do not currently have a gdb package built for msp430-elf, although I can make one. Please note that newlib is built with no debugging symbols. I can build gdb for msp430-elf and do some testing on my own, but it would help if you provided a Makefile and a minimal example showing where you encounter the problem. Thank you. Cheers, Orlando.

kl1278 commented on 2015-09-28 03:35 (UTC)

Compiling using generated msp430-elf-gcc using -gstabs gave correct results for debugging. When using -gdwarf, gdb complains with this error: 'Single stepping until exit from function main, which has no line number information.' Examining the elf file with 'readelf --debug-dump=decodedline test.elf' showed no line numbers for my source files. Turning off garbage collection on sections produced line numbers with readelf, but still the same error in gdb about no line numbers. Anyway, -gstabs is working for now.

kl1278 commented on 2015-09-27 08:01 (UTC)

It installed without a glitch. Afterward it compiled my msp430 project without a problem. Debugging however was not possible as it gave me an error about missing line numbers. I tried it with gdb 7.10 and gdb 7.7. So I had to revert back to the the TI provided Compiler (MSP430-GCC 3_05_00_00). Same makefile, this time no errors. Any ideas?

« First ‹ Previous 1 2 3