[Feature Request] Standalone "Java Stack Trace Console" (paste-and-navigate stack traces, independent of an active debug session)

[SougandhS]

Developers frequently receive Java stack traces from log files, CI failures, bug reports, chat messages, and production logs. Eclipse JDT has a "Java Stack Trace Console" — you paste any Java stack trace into it (from a log file, CI, a bug report, etc.) and each frame becomes a clickable link that jumps to the source line. It works without a running debug session.

VS Code doesn't have this today. The closest existing request, #506, only covers stack traces printed live in the Debug Console during an active session — it doesn't help when you just have a trace from somewhere else and want to navigate it.

The main challenge is resolving a class name to the right source file (multiple projects with same-named classes, inner classes, lambdas, etc.). Eclipse already solves this in JavaStackTraceHyperlink.java

Related to eclipse-jdtls/eclipse.jdt.ls#3834

[github-actions]

Hi @SougandhS, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Suggestions

• Upvote or comment on existing feature requests:

  • vscode-java-debug#506: live Debug Console only supports stack hyperlinks during an active session. It’s the closest existing ask. Jump to source when clicking the call stack info in debug console #506
  • eclipse-jdt.ls#1202: adds a convert callstack entry to location LSP method that could serve as the backend for a standalone console. [Feature Request] Provide method for converting callstack entry to location eclipse-jdtls/eclipse.jdt.ls#1202 (comment)
  • eclipse-jdt.ls#3834: tracks broader support for stack-trace navigation outside of debug sessions. (Feature Request) Add support for JDT Debbuger and Test Infrastructure? eclipse-jdtls/eclipse.jdt.ls#3834
  • Enable Navigation to Classes from Debug Console redhat-developer/vscode-java#3867: enables Ctrl+Click navigation from the Debug Console. Enable Navigation to Classes from Debug Console redhat-developer/vscode-java#3867

• Reference Eclipse’s implementation for parsing and hyperlinking:

  • JavaStackTraceHyperlink.java – the parsing logic and hyperlink resolution used by Eclipse JDT. https://github.com/eclipse-jdt/eclipse.jdt.debug/blob/master/org.eclipse.jdt.debug.ui/ui/org/eclipse/jdt/internal/debug/ui/console/JavaStackTraceHyperlink.java

• Workaround:

  1. Launch any Java debug configuration.
  2. Paste your stack trace into the Debug Console.
  3. Click the generated hyperlinks to jump to source.

• Contribution path:

  1. Create a VS Code extension with an OutputChannel for pasted text.
  2. Use LSP commands (java.resolveType / java.resolveSource) or the convert callstack entry to location API from The cursor should point to the starting column when hitting on inline breakpoint #1202 to resolve each frame.
  3. Render each frame as a clickable link that opens the file at the correct line.

Labels

• enhancement

Other references with low confidence

- #1133: “Support for copying complete stacks to the pasteboard” – related to console features but not directly navigation. https://github.com//issues/1133

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!