microsoft / microsoft/vscode-cpptools

Go to definition failing when done twice on symbol defined locally

Offen
#6,280 9 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

bug investigate: repro Language Service symlinks
Vorherrschende Sprache
TypeScript
Sterne
6.2k
Forks
1.7k
Ø Merge
14 Std. 46 Min.
Gemergte PRs (30 T.)
61

Beschreibung

Type: LanguageService

Describe the bug

  • OS and Version: Ubuntu 20.04
  • VS Code Version: 1.50.0
  • C/C++ Extension Version: 1.0.1
  • Other extensions you installed (and if the issue persists after disabling them): Remote - SSH (no)
  • Does this issue involve using SSH remote to run the extension on a remote machine?: No

Steps to reproduce

  1. Open a .cpp file
  2. Click on any symbol defined in the same opened file
  3. Go to definition (or Peek definition)
  4. This works (an editor, or the peek viewer, opens), and IntelliSense also works as expected (hovering shows definition, etc)
  5. Close the newly opened editor / peek viewer
  6. Click on any symbol (whatsoever) and go to definition
  7. No definition found for 'symbol'. Also, IntelliSense stops working (hovering does not highlight anything).
    This might be related to the fact that the
Logs (sorry for italian)
-------- Diagnostics - 8/10/2020, 20:49:13
Version: 1.0.1
Current Configuration:
{
    "name": "Linux",
    "includePath": [
        big list of paths
    ],
    "defines": [],
    "compilerPath": "compilerpath",
    "cStandard": "c11",
    "cppStandard": "c++14",
    "intelliSenseMode": "gcc-x64",
    "browse": {
        "limitSymbolsToIncludedHeaders": true,
        "path": [
            big list of paths
        ]
    },
    "compilerArgs": []
}
Translation Unit Mappings:
[ /path/to//myfile.cc. ]:
    /path/to//myfile.cc
Translation Unit Configurations:
[ /path/to//myfile.cc ]: not ready
    Process ID: 22754
    Memory Usage: 3 MB
    Compiler Path: compiler path
    Includes:
        big list of paths
    Standard Version: c++14
    IntelliSense Mode: gcc-x64
    Other Flags:
        --g++
        --gnu_version=80200
Total Memory Usage: 3 MB

------- Workspace parsing diagnostics -------
Number of folders and files enumerated: 21991
Number of files discovered (not excluded): 18112

# C++ log
ciclo inattivo: rianalisi del documento attivo
textDocument/hover: file:///path/to//myfile.cc (id: 26)
textDocument/hover: file:///path/to//myfile.cc (id: 27)
textDocument/hover: file:///path/to//myfile.cc (id: 28)
Arresto del server IntelliSense: /path/to//myfile.cc
terminazione del processo figlio: 22666
ancora attivo. Verrà terminato...
Il processo non è stato ancora terminato. Verrà sospeso per 10 millisecondi prima di riprovare.
Il processo non è stato ancora terminato. Verrà sospeso per 20 millisecondi prima di riprovare.
Il processo non è stato ancora terminato. Verrà sospeso per 40 millisecondi prima di riprovare.
Chiusura del canale di comunicazione.
Il client IntelliSense non è disponibile. Verrà usato il parser di tag per passare alla definizione.
Il client IntelliSense non è disponibile. Verrà usato il parser di tag per accedere alle informazioni rapide.
utilizzo del parser di tag per accedere alle informazioni rapide

Additional context
The file is quite big (~2000 lines), and the project is also big (as you can see from logs). It might be relevant that the project is accessed on an AFS mount.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Reproduzieren Sie den Fehler in einer .cpp-Datei, indem Sie zweimal Go to Definition oder Peek Definition verwenden, und untersuchen Sie die Ausgabe von C/C++ log und Log Diagnostics, wenn IntelliSense nicht mehr reagiert. Vergleichen Sie die erste erfolgreiche Suche mit der zweiten fehlgeschlagenen Suche und bestätigen Sie, dass die Definitionssuche und das Hovering nach dem Schließen des ersten Editors oder der ersten Peek-Ansicht weiterhin funktionieren.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
cpp
Bereich
devtools
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
42/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.