.h_set seem not stop when code is running

[Chaoyue Ying]

Settings document explain .h_set handle will be called when the value is loaded from persisted storage with settings_load().And I want to know how it work.

I put a breakpoint in  alpha_handle_set() that in settings sample.Then debug this sample.

But the project run finished immediately without stop at the breakpoint.

How the handle be called?

[Einar Thorsrud]

Did you build with debug optizmitation? If you build with default optimizations, stepping is often tricky as the actual optimized machine code could be quite different from the C code

[Chaoyue Ying]

This is mine build configuration.

[Einar Thorsrud]

Hi,

I see. I ran the sample now, and when I build with debug optimization and set a breakpoint oin the start of the alpha_handle_set() function in zephyr/samples/subsys/settings/src/main.c I see the debugger stopping on the breakpoint:

Are you not able to hit a breakpoint anywhere in this project? What about other projects? If this project, which exact line do you set the breakpoint on?

[Chaoyue Ying]

I retest this sample and add breakpoint at at the start of every function besides main,And I delete the breakpoint when code is stop.It still have some point be leaved.

You can also see that the end be send in log.

我重新测试这个示例，并在除main和I de之外的每个函数的开始处添加断点

[Einar Thorsrud]

Does that mean that no break-points are hit? Are you abelt o set breakpoint in other applications? Or does debugging with breakpoints not work at all in any applicaiton?

[Chaoyue Ying]

No,those point in the above picture all are not be bited.I delete those point that be hited.

In this sample,just  alpha_handle_set(), alpha_handle_export(), beta_handle_export() , direct_loader() and direct_loader_immediate_value() not hit.

Other functions like alpha_handle_commit() will stop application when breakpoint be set.

[Einar Thorsrud]

Hi,

I see. I am not able to explain or reproduce it. Does it happen if you do a full chip erase and run again? Also, is anything actually not working as expected, or is it only a problem with the debugging?

Are you able to debug other samples as expected (set breakpoints in the code and those are hit as they should etc)?