microsoft / microsoft/vscode-cpptools
Go to Definition jumps to .h declaration instead of .c definition in 1.33.2 (regression from 1.32.2)
Offen
@sean-mcmanus arbeitet bereits daran.
Seit 17.8.2026.
Feature: Go to Definition
Language Service
more info needed
regression
- Vorherrschende Sprache
- TypeScript
- Sterne
- 6.2k
- Forks
- 1.7k
- Ø Merge
- 14 Std. 46 Min.
- Gemergte PRs (30 T.)
- 61
Beschreibung
Environment
- OS: Windows 10 Pro for Workstations
- VS Code version: (your version)
- C/C++ extension version: 1.33.2 (broken), 1.32.2 (works)
- Project type: Embedded C firmware (esirisc architecture)
- Workspace on: mapped virtual drive (M:)
Problem
After upgrading to 1.33.2, pressing F12 (Go to Definition) on a function
always jumps to the declaration in the .h header file instead of the
implementation in the .c source file. Downgrading to 1.32.2 restores
correct behavior immediately.
Steps to Reproduce
- Open a C project on a mapped virtual drive
- Open a source file (e.g. FlowWork.c)
- Press F12 on a function call (e.g. AppFrontFilter())
- Expected: jumps to AppFrontFilter.c:929 (definition)
- Actual: jumps to AppFrontFilter.h:77 (declaration)
Additional Info
- The issue occurs even when the target .c file is open in the editor
- compile_commands.json is configured and loaded correctly (verified via Log Diagnostics)
- The browse database is fully built (verified via C/C++ Output channel)
- Downgrading to 1.32.2 fixes the issue without any other changes
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.