Reporting bugs

Have you really found a bug?

If you think you have found a bug in any part of the mspgcc toolchain, the first thing to do is look through the FAQ at this site. A number of bug reports are due to misunderstandings. If a quick scan of the FAQ answers your question, it saves everyone time - including yours.

Send a bug report

Remember mspgcc is built upon the standard GNU toolchain. If an internal error occurs many of the programs, you will receive a message telling you to report the problem to an e-mail address at gnu.org. Don't do this for now. When mspgcc is fully merged with the generic GNU toolchain those addresses will be the correct ones for bug reports. Right now reporting problems to those addresses will get you nowhere.

When submitting a bug report make sure you include:

• The OS you are using - e.g. Win XP, or RedHat 8.0. Just saying Windows is less helpful, as many issues are specific to particular versions of Windows.
• If you are using a prebuilt installer, the version of the installer you are using.
• If you built the mspgcc software yourself, the versions of the generic GNU tools you used, and the date on which you checked out code from the mspgcc CVS archive.
• Which MCU you are working with - e.g. MSP430F149
• The command line you used. A number of false bug reports are due to people using incorrect command line parameters. Tell us what you used and you may get a much quicker answer to your problem.
• If you are reporting a problem with the C compiler, a full preprocessed source listing. This can be created with a command like

  $ msp430-gcc [options] -E buggyfile.c > buggyfile.i
  
  

• If you are reporting a problem with the code generated by the C compiler, a full assembly language listing. This can be created with a command like

  $ msp430-gcc [options] -S buggyfile.c -dp