Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Unknown source debugging attached java process

Ouverte
  • Quelque chose ne va pas ?
#1,469 3 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
32/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
java, typescript, vscode
Domaine
devtools

Piste de recherche

Commencez par le fichier joint LanguageServerLogFile.txt et étudiez le chemin de résolution des sources Java lors de l’attachement à un processus, en utilisant les paramètres projectName et sourcePaths indiqués comme points d’entrée. Reproduisez le problème avec la configuration fournie si possible, puis vérifiez que le fichier Pos001.java ouvert est associé à l’emplacement dans la pile d’appels et que la ligne courante est mise en surbrillance.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

ai-triaged question

When attaching to a Java process built with a custom bazel-based build system, the Java debugger can't resolved source even though the file is open, reporting "Unknown source".

Environment
  • Operating System: Windows 11 Enterprise locally, Linux remotely.
  • JDK version: Adoptium Temurin-17 (tried 21 as well)
  • Visual Studio Code version: 1.85.2
  • Java extension version: v0.57.0
  • Java Debugger extension version: v0.26.0 (extension pack)
  • Language support for Java by Red Hat: v1.29.0
Steps To Reproduce
  1. Start Visual Studio Code and connect to the SSH host.
  2. In Terminal, build (using proprietary bazel-based build system).
  3. In Terminal, change to the directory where the result JARs are produced.
  4. Open the source file with the main function (Pos001.java, in this case).
  5. Create a java attach-to-process debugger config. No special settings, just type, name, request, processId set as:
    "type": "java", "name": "Java attach to process", "projectName": "acquiretokenbyuserid", "request": "attach", "processId":"${command:PickJavaProcess}",
  6. Run main in the target class using typical attach to process parameters as shown below. It is waiting for a keystroke.
    java -agentlib:jdwp=transport=dt_socket,server=y,address=5005 -verbose -cp "./*" packagename1.packagename2.Pos001
  7. In Visual Studio, attach to the process and set a breakpoint just after where the code is waiting for the keystroke.
  8. In the Terminal window where the process was run, press enter.

Logs: LanguageServerLogFile.txt
I can't provide source or project, sorry.

Current Result

Call stack reports Unknown source and the current source line is not highlighted. The call stack does correctly report the filename and line number of where the program is, so you can manually scroll through. Stepping through and further breakpoints work normally, just with this limitation.

Expected Result

Debugger should highlight the current line and recognize the open file in the editor as the correct source. Or at least, it should behave as Real Visual Studio, asking me "should I use this file?" or allowing me to browse for it.

Additional Informations
  1. Language Support for Java window reports several instances of the following:
    [Error - 6:19:42 PM] Apr 21, 2024, 6:19:42 PM _/lotus-qe/core-pfs/src/test/java/sts/acquiretokenbyuserid [in rpsmain2_f021ed] does not exist _/lotus-qe/core-pfs/src/test/java/sts/acquiretokenbyuserid [in rpsmain2_f021ed] does not exist Java Model Exception: Error in Java Model (code 969): _/lotus-qe/core-pfs/src/test/java/sts/acquiretokenbyuserid [in rpsmain2_f021ed] does not exist at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:562) at org.eclipse.jdt.internal.core.PackageFragmentRoot.getUnderlyingResource(PackageFragmentRoot.java:764) at org.eclipse.jdt.internal.core.PackageFragment.getUnderlyingResource(PackageFragment.java:430) at org.eclipse.jdt.internal.core.Openable.getUnderlyingResource(Openable.java:328) at org.eclipse.jdt.internal.core.CompilationUnit.getUnderlyingResource(CompilationUnit.java:975) at org.eclipse.jdt.ls.core.internal.handlers.BaseDiagnosticsHandler.collectNonJavaProblems(BaseDiagnosticsHandler.java:149) at org.eclipse.jdt.ls.core.internal.handlers.BaseDiagnosticsHandler.endReporting(BaseDiagnosticsHandler.java:135) at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.reportProblems(ReconcileWorkingCopyOperation.java:141) at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.executeOperation(ReconcileWorkingCopyOperation.java:110) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:740) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:805) at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1311) at org.eclipse.jdt.ls.core.internal.handlers.BaseDocumentLifeCycleHandler.publishDiagnostics(BaseDocumentLifeCycleHandler.java:332) at org.eclipse.jdt.ls.core.internal.handlers.BaseDocumentLifeCycleHandler.publishDiagnostics(BaseDocumentLifeCycleHandler.java:295) at org.eclipse.jdt.ls.core.internal.handlers.BaseDocumentLifeCycleHandler$PublishDiagnosticJob.run(BaseDocumentLifeCycleHandler.java:777) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
  2. There's no maven or gradle files in this project, it uses a custom bazel-based build.
  3. Disabled Maven and Gradle project import, but this seems to make no difference. Debugger appears built to require these.
  4. Set sourcePaths in debugger config, no help.
  5. If it matters, JDK is configured via java.jdt.ls.java.home in settings.json on remote host.
Langage dominant
TypeScript
Étoiles
591
Forks
429
Merge moyen
1 j 1 h
PR mergées (30 j)
20

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de microsoft/vscode-java-debug

Toutes les issues de microsoft/vscode-java-debug

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.