Describe the bug
Debugging an application inside a docker container gets stuck at the progress "Starting gdbserver".
Using a different debug target connecting to the already running gdbserver within the container (without building and uploading) works as expected.
The issue appears to be that the build/debug launch task blocks further execution of the debugger, preventing the connection from being established.
To Reproduce
Steps to reproduce the behavior:
- Pull a docker image with gcc, g++, make and gdbserver installed
- Create C/C++ Hello World Project
- Setup "Build inside Docker Image" in project settings -> C/C++ Build -> Settings -> Container Settings
- Enable "Build inside Docker Image"
- Select local docker socket
- Select previously pulled image
- Build project inside docker container to ensure the environment is set up correctly
- Try to debug application as C/C++ Container Application
- Process hangs at "Starting gdbserver" and thus gdb is not connecting
Note: Starting the container in privileged mode does not change the behaviour.
Expected behavior
- Starting a docker container mounting the project
- Run gdbserver with specified arguments
- Connect to running gdbserver
- Running debugging session
Version Information (please complete the following information):
- OS and OS Version/extra details: Debian 13.5
- Eclipse Version: 2026-03 (4.39.0)
- CDT Version: 12.4.0.202603041756
Describe the bug
Debugging an application inside a docker container gets stuck at the progress "Starting gdbserver".
Using a different debug target connecting to the already running gdbserver within the container (without building and uploading) works as expected.
The issue appears to be that the build/debug launch task blocks further execution of the debugger, preventing the connection from being established.
To Reproduce
Steps to reproduce the behavior:
Note: Starting the container in privileged mode does not change the behaviour.
Expected behavior
Version Information (please complete the following information):