We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
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?
Was the library built with debug info? Do C251 libraries even support debug info? Why is it a library is you want to step into it?
I have a workspace in which there are two projects,one is used to generate a lib file,the other will call this lib generated from C files of the first project?I think the lib have a problem, so I want to step into it, to step into Corresponding C files and to Verify my guess. I couldn't step into my C files of generated from lib, even if I added debugging information in lib, in the way "option for target\ouput\Debug information". set check mark?
I try to build a workspace in uvision 5.25.3.0,there are two projects in this workspace. one is testkeil_calllib,the other is testkeillib. testkeil_calllib calls testkeillib.lib generated from project testkeillib.when I debug,I can step into the testkellib.lib,debug in C files. now, I have another workspace,built in uvision 4.22.0.0,with two prjects,I can also step into C file 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.
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 ... ?