after update to 2026.01 remote debuging does not work

Hello!

Sorry for the delay in response.

1. Do I understand correctly that you have the following setup: CLion is installed on a Windows machine, compilation occurs in a WSL instance, and the resulting binary needs to be debugged on a separate remote machine?
2. Please go to Help | Diagnostic Tools | Debug Log Settings, add com.jetbrains.cidr.execution.debugger there, reproduce the issue, then do Help | Collect Logs and Diagnostic Data, upload the resulting archive to https://uploads.services.jetbrains.com/, and let us know the Upload ID. Do not forget to disable debug logging after that. Note that logs might contain private user information (like file paths and names).

Hallo

Thanks for checking the problem :)

1. CLion is installed on Windows machine, cross compilation occurs under Windows - using MinGW compiler suite. Resulting executable is uploaded to WSL and remote debugged using gdbserver/gdb. This setup is used to emulate actual target system running on remote linux machine (debugging on actual target system is possible but impractical)

2. uploaded logs from simple test project - after compilation added one breakpoint (no problems reported), and started debug session. After debugger loaded the executable breakpoint icon turned into stop sign and program started (i could see stdout on Console) - breakpoint didnt have any effect. Tried to puase the program - execution stoppped, source windows shown assembler code. Pressed continue - program continued.

When i open the same project using CLion 2025.3 everything works ok - programm stops on Breakpoint and Pasue “lands” in std::nanosleep  (as expected).

Upload id: 2026_08_03_bVyMbfwNZW1za23ykfYidR (file: clion-logs-20260803-13505610849244464886118602.zip)

Gdomagala, thank you for the provided details!

I have a few follow-up questions:

1. Could you please clarify why you cross-compile a binary on Windows rather than compile it in WSL using the WSL toolchain?

2. Please check what debug profile and run/debug configuration are selected on the toolbar when you launch a debugging session in CLion 2026.2.0.1:

   

   Then, please provide screenshots of the selected debug profile from File | Settings | Build, Execution, Deployment | Debugger | Debug Profiles and the selected run/debug configuration from Run | Edit Configurations…. 

1. Mostly because real projects use custom tooling that is not (yet) available on WSL. 

2.

Gdomagala, 

1. Just to double-check: is the Credentials field really empty in your Remote GDB Server configuration? Is it also empty in CLion 2025.3.6?
2. Do you have port forwarding configured between a local machine and a WSL instance?
3. Please run "C:\Program Files\JetBrains\CLion 2026.2.0.1\bin\gdb\win\x64\bin\gdb.exe" <path to your binary on Windows> in Command Prompt, then execute the info sources command and share the output.

1. Sorry - when im switchin between 2025 and 2026 it sometimes resets credential and i forgot to update them before taking screenschot.

Updated screenschot:

As you see - debugger is connected, test program runs - just the 2 breakpoints are deactivated for some reason.

2. WSL is configured to run with port mirroring. .wsconfing file looks like this:

[wsl2]
networkingMode=mirrored
firewall=false

ssh and gdbserver are reachable from host (works perfectly with Clion 2025).

3.

with gdb from CLion 2026:

No symbol table is loaded.  Use the "file" command.

with gdb from CLion 2025 (the same file):

D:\WORK\VISIGO\MACHINES\MinimalProject\MAIN\ARM\build\vm-debug\MinimalProject_65.dbg:
(Full debug information has not yet been read for this file.)

/home/ctng/.build/HOST-x86_64-w64-mingw32ucrt/i686-ubuntu18.04-linux-gnu/src/glibc/csu/../sysdeps/i386/start.S,
/home/ctng/.build/HOST-x86_64-w64-mingw32ucrt/i686-ubuntu18.04-linux-gnu/src/glibc/csu/init.c,
/home/ctng/.build/HOST-x86_64-w64-mingw32ucrt/i686-ubuntu18.04-linux-gnu/src/glibc/csu/../sysdeps/i386/crti.S,
D:\WORK\VISIGO\MACHINES\MinimalProject\MAIN\ARM\Dummies\Kernel.cpp,
+ dozens other files

Looks like gdb distributed with 2026 dosent support this file format/architecture. 

Updated Debug config to use gdb provided in 2025 version and everything seems to work. Maybe not a cleanes solution but works for me :)

Gdomagala, thank you for the update! I'm glad to hear you found the workaround!

I've spoken with the responsible developer. According to him, CLion 2026.2.1 will include some fixes that might help with the issue you're facing. 

CLion 2026.2.1 is scheduled for release this week. Please update CLion when it becomes available, try using the bundled GDB in CLion 2026.2.1, and let us know if the issue is resolved for you.