C/C++V1.22.11， Clicking on a function cannot jump to the function implementation of another file, it can only jump to the declaration of the head file #13078
Comments
|
Yes, the issue is that the file with definition is not getting "tag parsed" and the symbol added to our database. When you open the file and save it, that appears to trigger the tag parse and database update. If you set C_Cpp.loggingLevel to "Debug" and check your C/C++ logs after running the "Rescan Workspace" command you should check to see if the "Processing folder " logging includes the folder that has the definition. Then you can try running the Reset IntelliSense Database command, which could fix the issue if your database is in a bad state, otherwise, you can look for "tag parsing file" messages and see if you notice which files are not getting parsed. You might have a files.exclude set. |
sean-mcmanus
added
Language Service
more info needed
|
loggingLevel: Debug |
|
loggingLevel: Debug 标记分析文件: D:\Product\GSP-6Pro-Pdf\Drivers\FM33LC0xx_FL_Driver\fm33lc0xx_fl_rtc.h 标记分析文件: C:\Program Files (x86)\Windows Kits\10\Include\10.0.20348.0\shared\apisetcconv.h 标记分析文件: D:\Product\GSP-6Pro-Pdf\Drivers\FM33LC0xx_FL_Driver\fm33lc0xx_fl_rtc.h When I installed version v1.21.6, the output log. It's normal now. You can jump to the function definition now. |
sean-mcmanus
added
bug
and removed
more info needed
|
@fxliuqq Your logging indicates that Are the files under D:\PRODUCT\GSP-6PRO-PDF\APPLICATION in a non-UTF-8 file encoding? Can you try 1.23.2 (pre-release) and then run the Reset IntelliSense Database command? We fixed some bugs related to non-UTF-8 file encoding handling in that release. |
sean-mcmanus
added
world ready
|
The 1.23.2 (pre release) version also does not work when resetting the IntelligenceDatabase There are GB2312 files in the folder. |
|
Hi, @fxliuqq . Are you using the setting |
|
|
|
I have always set it this way, V1.21.6 can be used normally, but V1.22.9, V1.22.10, and V1.22.11 are not, and cannot jump across files normally. |
|
Hi @fxliuqq . Since you have |
|
I just tried V1.21.6, but upgrading to V1.22.0 doesn't work. |
|
stm32.zip |
|
Hi @fxliuqq . The repro you provided requires dependencies I don't have, such as Keil_v5. I tried installing We do have some file encoding fixes coming in 1.23.3, which will be released within a day or two. Using your files (without C:\Keil_v5 present, and after adding a |
|
Keil5.37 and later versions no longer have ARMCC. Okay, I'll try installing the next version later. |
|
I just used V1.23.3 and the function jump has been improved, but there were still a few unsuccessful jumps. But there will be many defined macros and global variables that cannot be recognized and redirected. |
|
The 'problems' reported in your image appear to be IntelliSense errors. If the code builds, IntelliSense errors are often due to the IntelliSense configuration not matching how the code is actually built. You can use the You might try configuring the extension by taking a working full compile command line (perhaps from a log of a successful build) and use that in the Otherwise, if you could isolate/reduce any of the remaining issues you're seeing, we could take a look at them individually. |
|
I created a program based on ARM microcontroller using Keil (MDK). VSCode has a plugin called Keil uVision Assistant, which imports the Keil environment program into VS and automatically generates a JSON file. Currently, V1.21.6 can be used normally.
|
|
Hi @fxliuqq . I think you may be getting more correct (error) results with 1.23.3. I am seeing similar issues with the For instance, in I also see some errors, such as in I do see some strange issues with |
|
Now switching back to V1.21.6, everything is normal
|
Environment
Bug Summary and Steps to Reproduce
C/C++V1.21.6 can be used normally, but C/C++V1.22.9, C/C++V1.22.10, and C/C++V1.22.11 cannot be used normally. Clicking on the function will redirect the function to the declaration of the header file if it is in the current file, but if the implementation of the function is not in the current file, it will only redirect to the declaration of the header file.
Configuration and Logs
{ "configurations": [ { "name": "RC-17", "includePath": [ "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\Drivers\\CMSIS\\Device\\FM\\FM33xx\\Include", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\MF-config\\Inc", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\Inc", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\APP\\inc", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\Drivers\\FM33LC0xx_FL_Driver\\Inc", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\Drivers\\Library\\Core", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\Middleware\\USB\\App\\inc", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\Drivers\\Library\\Device", "C:\\Keil_v5\\ARM\\ARMCC\\include", "C:\\Keil_v5\\ARM\\ARMCC\\include\\rw", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\Drivers\\CMSIS\\Device\\FM\\FM33xx\\Source\\Templates\\arm", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\MF-config\\Src", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\Src", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\APP\\src", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\Drivers\\CMSIS\\Device\\FM\\FM33xx\\Source", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\Drivers\\FM33LC0xx_FL_Driver\\Src", "c:\\Users\\lqq\\Documents\\WXWork\\1688856331479903\\Cache\\File\\2024-12\\RC-17-V5.1(2)\\RC-17-V5.1\\APP\\Middleware\\USB\\App\\src", "${default}", "${workspaceFolder}/**" ], "defines": [ "FM33LC0XX", "USE_FULL_ASSERT", "MFANG", "__CC_ARM", "__arm__", "__align(x)=", "__ALIGNOF__(x)=", "__alignof__(x)=", "__asm(x)=", "__forceinline=", "__restrict=", "__global_reg(n)=", "__inline=", "__int64=long long", "__INTADDR__(expr)=0", "__irq=", "__packed=", "__pure=", "__smc(n)=", "__svc(n)=", "__svc_indirect(n)=", "__svc_indirect_r7(n)=", "__value_in_regs=", "__weak=", "__writeonly=", "__declspec(x)=", "__attribute__(x)=", "__nonnull__(x)=", "__register=", "__breakpoint(x)=", "__cdp(x,y,z)=", "__clrex()=", "__clz(x)=0U", "__current_pc()=0U", "__current_sp()=0U", "__disable_fiq()=", "__disable_irq()=", "__dmb(x)=", "__dsb(x)=", "__enable_fiq()=", "__enable_irq()=", "__fabs(x)=0.0", "__fabsf(x)=0.0f", "__force_loads()=", "__force_stores()=", "__isb(x)=", "__ldrex(x)=0U", "__ldrexd(x)=0U", "__ldrt(x)=0U", "__memory_changed()=", "__nop()=", "__pld(...)=", "__pli(...)=", "__qadd(x,y)=0", "__qdbl(x)=0", "__qsub(x,y)=0", "__rbit(x)=0U", "__rev(x)=0U", "__return_address()=0U", "__ror(x,y)=0U", "__schedule_barrier()=", "__semihost(x,y)=0", "__sev()=", "__sqrt(x)=0.0", "__sqrtf(x)=0.0f", "__ssat(x,y)=0", "__strex(x,y)=0U", "__strexd(x,y)=0", "__strt(x,y)=", "__swp(x,y)=0U", "__usat(x,y)=0U", "__wfe()=", "__wfi()=", "__yield()=", "__vfp_status(x,y)=0" ], "intelliSenseMode": "${default}" } ], "version": 4 } Logs There is no log output when using C/C++V1.22.11, while using C/C++V1.21.6 will output a lot of informationOther Extensions
Additional context
I found that the file containing the function that cannot be jumped to will not list the function list. It is necessary to modify some of the content of the file and save it, so that the file can list the function list and jump to it. Therefore, I believe that Intellisense will become invalid and there will be no automatic recognition of files in the workspace. It is necessary to manually change the file to trigger the recognition file and recognition function.
The text was updated successfully, but these errors were encountered: