vscode-rdbg: attach mode doesn't work on v0.2.0 with bash
Hello, thank you a lot for this awesome extension!
I think vscode debugging for attach mode had worked until yesterday or the day before yesterday.
But after releasing v0.2.0 (maybe), when I start debugging this dialog appears and failed to start debugging.
bash: cannot set terminal process group (173): Inappropriate ioctl for device
bash: no job control in this shell
And, output tab for rdbg says same messages.
My environment
- Ruby = v3.2.0
- Rails = v7.0.4.2
- rdbg = v.1.7.1
- docker-compose (Docker = v20.10.11, docker-compose = v1.29.2)
- Dev Containers extension v0,292.0
- Windows WSL2 (Ubuntu 20.04)
docker-compose.yml
services:
api
# ...
command: /bin/sh -c "rm -f tmp/pids/server.pid && rdbg --nonstop --open --command -- rails server --binding=0.0.0.0"
launch.json
{
"version": "0.2.0",
"configurations": [
{
"type": "rdbg",
"name": "Attach with rdbg",
"request": "attach"
}
]
}
v0.1.0 works
After reinstalling v0.1.0, debugging for attach mode has worked again.
Do I overlook something to use v0.2.0 for attach mode?
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 1
- Comments: 15 (1 by maintainers)
Commits related to this issue
- Do not reject only if err is occurs Close #250 "bash: no job control in this shell process" is outputted into stdout when running the bash command. In this case, we can ignore this message since the... — committed to ono-max/vscode-rdbg by ono-max a year ago
- Do not reject only if err is occurs Close #250 "bash: no job control in this shell process" is outputted into stdout when running the bash command. In this case, we can ignore this message since the... — committed to ono-max/vscode-rdbg by ono-max a year ago
- Reject promise only if an error occurs Close #250 "bash: no job control in this shell process" is outputted into stdout when running the bash command. In this case, we can ignore this message since ... — committed to ono-max/vscode-rdbg by ono-max a year ago
- Use shell option when running a child process If we configure `shell` option, the command are executed inside of a shell. Thus, we do not need to make a shell command. This PR also fixes ruby#250. S... — committed to ono-max/vscode-rdbg by ono-max a year ago
- Use shell option when running a child process If we configure `shell` option, the command are executed inside of a shell. Thus, we do not need to make a shell command. This PR also fixes ruby#250. S... — committed to ono-max/vscode-rdbg by ono-max a year ago
- Use shell option when running a child process If we configure `shell` option, the command is executed inside of a shell. Thus, we do not need to make a shell command. This PR also fixes ruby#250. Se... — committed to ono-max/vscode-rdbg by ono-max a year ago
- Reject promise only if an error occurs Close #250 "bash: no job control in this shell process" is outputted into stdout when running the bash command. In this case, we can ignore this message since ... — committed to ruby/vscode-rdbg by ono-max a year ago
I have confirmed attach mode is working now on v0.2.1!!
Thank you so much @ono-max !
The new version has been released. If you still have a problem, please mention me or create the issue. Thank you.
I have the same issue running on MacOS [13.3.1 (a) (22E772610a)] on an M1 Macbook pro.
And to attach I have this configuration in my launch.json:
I get the message:
I am able to fully debug if I use the launch configuration (for local ruby and remote ruby files). But with the latest version (
v0.2.0) I am getting the above error.@ono-max So sorry I didn’t realized the issue was related to bash only. I changed my login shell to bash and the issue is fixed in version 0.2.1 when using bash as the login shell on macOS.
There is an issue with zsh on macOS however. I will create a new issue for this.
Thank you for your corporation. I think that https://github.com/ruby/vscode-rdbg/pull/259 fixes it.