0

After setting breakpoints in my code and then debugging, I am given the error stated in the question title and manually interrupting the program results in a console message, "No source available for "__muldf3() at 0x80006be" (as an example), possibly indicating that there is no debug source code to reference.

I have tried cleaning, rebuilding and restarting TrueSTUDIO. I have set my build configuration to debug. I have made sure that the .elf file is correct.

I don't know why my debug source files might be unmatched with my build code. Is there something or some setting which I am neglecting to change?

Milo Fan
  • 1
  • 1

1 Answers1

0

__muldf3() and in fact, most if not all the symbols with double scores prefix are "internal functions known to the compiler". In this particular case __muldf3 multiplies double arguments. You get this particular error because you are "randomly" breaking the debugger so the program pauses at wherever point it was at. In this case, it happened to be inside __muldf3. Since the library source code is not available in your particular setup, you get the "no source" error.

As for the "Breakpoint attribute problem: installation failed", I have not seen this error myself, and certainly it's pretty opaque on what it is complaining about. Please check that you are doing a debug build, and please clarify whether the debugger stops at main (as it should), even with this error. Web searches indicate that this error could be ignored if it does not stop you from using the debugger otherwise.

  • Sorry, just noticed some of the earlier replies that indeed the debugger does not stops at any of the breakpoint. It is possible that the actual program has not been flashed onto the chip. Use ST's ST-LINK utility and does a verify with the project output to make sure indeed TrueStudio has done the flashing correctly. – Richard at ImageCraft May 02 '19 at 07:24