This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software: TI C/C++ Compiler
Hi,
We have a custom firmware update scheme, where we write a checksum the .out file using.
msp430-elf-gdb --write --se firmware.out
This works with msp430-gcc 5.3.0.219 and msp430-gcc 5.3.0.224. But newer versions like 6.2.1.16 and 6.4.0.032 crash on exit. The problem can be reproduced on both macOS and windows (not tested on Linux).
Steps to reproduce
1) start GDB with --write option load any .out file
2) quit
Below is an example from macOS.
On windows, we get a dialog box saying that the program stopped working, asking if the debugger should be started.
Are there any workarounds for this problem besides using the old toolchains?
Thanks and regards,
-Asger
echo quit | /Applications/ti//ccs710/ccsv7/tools/compiler/msp430-gcc-6.4.0.32_osx/bin/msp430-elf-gdb --write --se foo.out
GNU gdb (SOMNIUM Technologies Limited - msp430-gcc 6.4.0.32) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-apple-darwin15.6.0 --target=msp430-elf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from foo.out...done.
(gdb) Segmentation fault: 11
I intend to file a defect report in the SDOWP system. Before I can do that, some changes need to be made in the SDOWP system. All of that is being worked through. I apologize for the delay.
Thanks and regards,
-George
Thank you for letting us know about the problem. I filed MSPGCC-1 in the SDOWP system to have this investigated. You are welcome to follow it with the SDOWP link below in my signature.
Thanks and regards,
-George
Asger Overby said:I'm unable to find the id "MSPGCC-1" in your tracking system.
It's there now. Please try again.
Unfortunately, you will see that no work has been done yet.
Thanks and regards,
-George