Lucee Debugger Extension in VSCode

michaeldiederich · May 6, 2026, 9:12am

I installed the extension davidrogers.luceedebug, but it shows the version 2.0.12.
When i configure the launch.json, the property secret is not allowed.
I downloaded the source code, build the extension and replaced the files with the new files. Then the extension didn’t start:

Debug adapter process has terminated unexpectedly (Extension host shut down)
I deleted the extension, restarted vsc and installed the extension from marketplace again.
With version 2.0.12, I call > luceedebug: show class and breakpoint info:

Breakpoints luceedebug has:
  (ide)    /Users/mmmm/Documents/xxx/yyy/abc/index.cfm:4 (unbound)
  (server) /home/abc/index.cfm:4 (unbound)

Path transforms:
  PrefixPathTransform{idePrefix='/Users/mmmm/Documents/xxx/yyy/abc/', serverPrefix='/home/abc'}

Files luceedebug knows about (all filenames are as the server sees them, and match against breakpoint 'server' paths):

(Before I build the extension manually, I saw some files…, so I guess i broke it…)

My questions: Is a the new extension in the market place to use?
How can I get this run?
curl/nmap says, the port 10000 is running/open on localhost

OS: MacOS with lucee running in docker
Lucee Version: 7.1.0.115-SNAPSHOT

Zackster · May 6, 2026, 1:15pm

Try the v3 Lucee version?

michaeldiederich · May 8, 2026, 7:09am

Sorry, was not clear from my side:

I downloaded the source code, build the extension and replaced the files with the new files. Then the extension didn’t start:
Debug adapter process has terminated unexpectedly (Extension host shut down)

I build and installed v3 again, now the extension is running:

luceedebug: show class and breakpoint info shows my set breakpoint at index.cfm and 730 files

I request the index.cfm in the browser and the pages loads, loads, loads and nothing happens. The watch/variables in the IDE are not populated. The small menu bar with “Continue / Step Over / Step Into” is shown and after some seconds the debugger stops. The page then loads as ususal.

I restarted the IDE and now luceedebug: show class and breakpoint info shows my unbound breakpoint and no more files.

I use the docker to mount server folders into one folder:

volumes:
      - ${myfolder}:/home/project_1/
      - ${myfolder}:/home/project_2/

The server.xml:

<Host name="project1" appBase="webapps">
<Context path="" docBase="/home/project_1"
</Host>
...

The launch.json:

PrefixPathTransform{idePrefix='/Users/.../project_x', serverPrefix='/home/project1'}
...

How can I get the debugger running? Thanks for your help!

michaeldiederich · May 8, 2026, 7:29am

nevermind, i found it:

I still had the old debugger in the setenv.sh enabled, so the port 10000 was used by the old debugger. I removed the file, removed the old luceedebugger.jar and rebuild docker.

the Debug Console now shows:

[luceedebug] luceedebug 3.0.0.5-SNAPSHOT connected to Lucee 7.1.0.116-SNAPSHOT
[luceedebug] Registered native debugger listener
...

The variables and watch-scope is populated and everything is running. A perfect timing, I need the debugger today really…

michaeldiederich · May 8, 2026, 7:49am

Ok, one last issue. When i debug and read the variables scope:

[luceedebug] ERROR: Launcher future exception: java.lang.StackOverflowError
java.util.concurrent.ExecutionException: java.lang.StackOverflowError
	at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
	at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor$1.get(ConcurrentMessageProcessor.java:54)
	at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor$1.get(ConcurrentMessageProcessor.java:50)
	at org.lucee.extension.debugger.DapServer.createForSocket(DapServer.java:258)
	at org.lucee.extension.debugger.extension.ExtensionActivator.lambda$new$0(ExtensionActivator.java:83)
	at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.StackOverflowError
	at lucee.commons.collection.concurrent.ConcurrentHashMapNullSupportJDK$EntrySetView$1$1.hashCode(ConcurrentHashMapNullSupportJDK.java:464)
	at lucee.commons.collection.concurrent.ConcurrentHashMapNullSupportJDK.hashCode(ConcurrentHashMapNullSupportJDK.java:634)
	at lucee.runtime.type.StructImpl.hashCode(StructImpl.java:358)
	at lucee.commons.collection.concurrent.ConcurrentHashMapNullSupportJDK$EntrySetView$1$1.hashCode(ConcurrentHashMapNullSupportJDK.java:464)
	at lucee.commons.collection.concurrent.ConcurrentHashMapNullSupportJDK.hashCode(ConcurrentHashMapNullSupportJDK.java:634)
	at lucee.runtime.type.StructImpl.hashCode(StructImpl.java:358)
	at lucee.commons.collection.concurrent.ConcurrentHashMapNullSupportJDK$EntrySetView$1$1.hashCode(ConcurrentHashMapNullSupportJDK.java:464)
	at lucee.commons.collection.concurrent.ConcurrentHashMapNullSupportJDK.hashCode(ConcurrentHashMapNullSupportJDK.java:634)
	at lucee.runtime.type.StructImpl.hashCode(StructImpl.java:358)
	at lucee.commons.collection.concurrent.ConcurrentHashMapNullSupportJDK$EntrySetView$1$1.hashCode(ConcurrentHashMapNullSupportJDK.java:464)
	at lucee.commons.collection.concurrent.ConcurrentHashMapNullSupportJDK.hashCode(ConcurrentHashMapNullSupportJDK.java:634)
	at lucee.runtime.type.StructImpl.hashCode(StructImpl.java:358)
	at lucee.commons.collection.concurrent.ConcurrentHashMapNullSupportJDK$EntrySetView$1$1.hashCode(ConcurrentHashMapNullSupportJDK.java:464)
	at lucee.commons.collection.concurrent.ConcurrentHashMapNullSupportJDK.hashCode(ConcurrentHashMapNullSupportJDK.java:634)
	at lucee.runtime.type.StructImpl.hashCode(StructImpl.java:358)
	at lucee.commons.collection.concurrent.ConcurrentHashMapNullSupportJDK$EntrySetView$1$1.hashCode(ConcurrentHashMapNullSupportJDK.java:464)
	at lucee.commons.collection.concurrent.ConcurrentHashMapNullSupportJDK.hashCode(ConcurrentHashMapNullSupportJDK.java:634)
	at lucee.runtime.type.StructImpl.hashCode(StructImpl.java:358)
....

Zackster · May 9, 2026, 4:37pm

thanks for the bug report

Zackster · May 21, 2026, 8:44am

Any feedback?

michaeldiederich · May 21, 2026, 9:02am

Well, I often have the problem, the variables/watches disappear. I also have to click “stop over” twice to get to the next line.
Sometimes there is a “Frame not found: 235” or other line in the watch-area, when the Variables disappear.

Zackster · May 21, 2026, 2:23pm

both should be fixed, give it a go and let me know

This fix only affects the native extension, older agent unchanged

github.com

lucee/extension-debugger/blob/main/CHANGELOG.md

# Changelog

## [3.0.0.7-SNAPSHOT] - 2026-05-21

### Fixed

- **[LDEV-6335](https://luceeserver.atlassian.net/browse/LDEV-6335)**: native step-over now advances by source line rather than by ExecutionLog instrumentation block — multi-expression lines (e.g. `<cfset c = a & b>`) no longer require two clicks to advance past
- **[LDEV-6334](https://luceeserver.atlassian.net/browse/LDEV-6334)**: stale frame IDs after step/continue resolve to the owning request's live `PageContext` via `requestId` matching, so racing VSCode requests no longer return "Frame not found" or blank the Variables panel

### Changed

- Minimum Lucee core version raised to **7.1.0.132**

## [3.0.0.6-SNAPSHOT] - 2026-05-09

### Fixed

- **[LDEV-6309](https://luceeserver.atlassian.net/browse/LDEV-6309)**: `StackOverflowError` when inspecting variables containing self-referential structs. `ValTracker.wrapperByObj` now uses identity-keyed weak references instead of `WeakHashMap`, so registering an object no longer triggers `StructImpl.hashCode()`'s value-walk on cyclic graphs.

## [3.0.0.5-SNAPSHOT] - 2026-04-23

This file has been truncated. show original

michaeldiederich · May 21, 2026, 3:25pm

I updated lucee to .133-SNAPSHOT and the extension to .7-SNAPSHOT and now I cannot set any breakpoints.

Breakpoints luceedebug has:


Path transforms:
  [4x Path mapping skipped]

Files luceedebug knows about (all filenames are as the server sees them, and match against breakpoint 'server' paths):

[luceedebug] luceedebug 3.0.0.7-SNAPSHOT connected to Lucee 7.1.0.133-SNAPSHOT
[luceedebug] Path mapping: IDE=...
[luceedebug] Path mapping: IDE=...
[luceedebug] Path mapping: IDE=...
[luceedebug] Path mapping: IDE=...
[luceedebug] Exception breakpoints: none
(once:)

[luceedebug] java.lang.OutOfMemoryError: Java heap space
  at unknown
[luceedebug] java.lang.OutOfMemoryError: Java heap space
  at unknown

If I request a (missing) page:

[luceedebug] missinginclude: Page [/foobar.cfm] [/home/xyz/foobar.cfm] not found
  at ...
[luceedebug] expression: Page request is aborted

What details do you need to debug?
If I type anything in the debugConsole, there is a “missing frameID”

Zackster · May 21, 2026, 3:55pm

Which version of Lucee 7.1 were you running before .133?

Setting "logLevel": "debug" in your launch.json should give a lot more useful info in the Debug Console.

Setting LUCEE_DEBUGGER_DEBUG=true (env var on the server) will also add a lot more detail to the server console logs

michaeldiederich · May 22, 2026, 5:48am

I used 7.1.0.125-SNAPSHOT

[luceedebug] luceedebug 3.0.0.7-SNAPSHOT connected to Lucee 7.1.0.133-SNAPSHOT
[luceedebug] Path mapping: IDE=...
[luceedebug] DEBUG: createTemporaryPageContext failed: null
[luceedebug] DEBUG: getExecutableLines: no PageContext available
[luceedebug] DEBUG: createTemporaryPageContext failed: null
[luceedebug] DEBUG: getExecutableLines: no PageContext available
[luceedebug] DEBUG: createTemporaryPageContext failed: null
[luceedebug] DEBUG: getExecutableLines: no PageContext available
[luceedebug] DEBUG: setFunctionBreakpoints: 0 breakpoints
[luceedebug] DEBUG: Function breakpoints cleared
[luceedebug] DEBUG: setExceptionBreakpoints: filters=[]
[luceedebug] Exception breakpoints: none
[luceedebug] DEBUG: Thread listing: 1 threads
[luceedebug] DEBUG: createTemporaryPageContext failed: null
[luceedebug] DEBUG: getExecutableLines: no PageContext available

I added the debug flag to docker and rebuild docker with the Version .133 & luceedebug 3.0.0.7 and now it works again. “Step over” works too.
I will test it today, but I guess there will be no more issues from my side.

Thank you very much, I really appreciate this tool.