Community
cancel
Showing results for 
Search instead for 
Did you mean: 
SBioo
Beginner
397 Views

Kernel stop right at the "printf" command.

I have design which behaves weird in one specific situation, and stops progressing, which I don't know the reason.

 

In this design I have added "printfs" to the non-autorun kernels to track the behavior of each single kernel. Interesting I have a kernel as below:

 

Screenshot from 2019-06-25 13-48-37.png

 

As I run this kernel and dump the output to a file, I can see that the logs are ending like this:

 

Screenshot from 2019-06-25 13-51-00.png

 

As you can see, the log ends with "plate=2047". In the code we know that we have another "printf" after this one, right away. Logically that "printf" should definitely do the printing and then maybe the blocking happens?

 

Any idea what is going on? and how this problem can be addressed?

 

Thanks

Tags (1)
0 Kudos
1 Reply
HRZ
Valued Contributor II
59 Views

Have you checked the beginning of the log to see how it starts? The compiler might have reordered your printfs. Printf output is dumped after kernel execution, which means your kernel must have executed all the code and exited if you are getting printf output.

Reply