cancel
Showing results for 
Search instead for 
Did you mean: 

Debug: No source available for "__floatdisf() at 0x800216e"

AKozarzewski
Associate II

Split from old thread Debug: "No source available for main()"

This is not the same question.


Little late to the party but I have the same issue kinda. I switched to other branch in our project and I had the very same result. Then I took all suggested steps and I get when I tried to debug:

No source available for "__floatdisf() at 0x800216e"

 

Besides after switching to that branch program compiles just fine but doesn't work. All of this is of some settings that remained in project and weren't covered in git commit, but it's hard to commit every single file in CubeIDE enviroment. All important files were covered like all code files and ioc etc. i always switch when Cube is not running because it also creates issues. Any ideas?

2 REPLIES 2
Andrew Neil
Super User

@AKozarzewski wrote:

I have the same issue kinda.?


Not really.

The old thread was about not finding the source for main() - the user's own code

 


@AKozarzewski wrote:

I get when I tried to debug:

No source available for "__floatdisf() at 0x800216e"?


That's a compiler library function - not your own code.

You wouldn't expect to have the source for compiler library functions

 

Please give some more details about your project, and what steps you take to get that message.

 

How to write your question to maximize your chances to find a solution

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.
Ozone
Principal III

> Besides after switching to that branch program compiles just fine but doesn't work. 

I think it would be helpful to provide a bit more information about what is not working.

As mentioned, most C-lib functions are not available in source, and thus not debuggable on C source level.
I think this is unrelated to the issue - but you can step through the assember instructions if needed.

Check were the application hangs, either by step-wise debugging, or retrospectively evaluate the SCB registers in case of a (hard-) fault.