uVison V5.25.3.0 c Compiler C251 V5.60.0.0. when I want to step into a library functions,keil gets into assembly wondows automatically during debugging, although I have the corresponding library function source code. why?
I think it is a bug of keil5 I have a workspace,built in uvision 4.22.0.0,with two prjects,one is testlib.uvproj,another is testcalllib.uvproj.I can also step into C files of lib file.but when I open this workspace in the uvision 5.25.3.0,built projects in the workspace.when I debug ,I can not step into C files of the lib file. after stduy this problem for one day,I can step into C files generating lib.I found that the path of C files generating lib in project file testlib.uvproj must use absolute path instead of relative path. why? I think it is a bug of keill5.
"I found that the path of C files generating lib in project file testlib.uvproj must use absolute path instead of relative path". How, exactly, did you determine that? Are you sure it's not just that you got your relative paths wrong ... ?