Should not suspend on detached mode
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
The issue names detached execution, binding.bp, and the exe/rdbg -O target.rb -n entry point, but no implementation file or test. Start by tracing how detached sessions handle binding.bp and compare the expected behavior with the current remote-console wait. Done means an agreed configuration scope, implemented behavior, and tests covering the selected default and option.
Written by the indexing model from the issue text.
Description
Now, detached debuggee encounters the suspend point (like binding.bp), the debuggee will suspend and wait for remote console connection like that:
p 1
binding.bp
[master]$ exe/rdbg -O target.rb -n
DEBUGGER: Session start (pid: 11257)
DEBUGGER: Debugger can attach via UNIX domain socket (/home/ko1/.ruby-debug-sock/ruby-debug-ko1-11257)
1
DEBUGGER: wait for debuger connection...
However, other deubgers like gdb doesn't stop (from the beginning, the detached process is not under control by gdb).
I think there is a case to wait remote console connection, but not sure which is majority.
Make a configuration?
- global configuration (which should be a default?)
binding.bpoption (wait_attach: true/false)
- Dominant language
- Ruby
- Stars
- 1.3k
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ruby/debug
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Support exceptionOptions in setExceptionBreakpoints to catch arbitrary exception classes via DAP Open
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
バグ
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
voxpupuli/puppet-epel#186 · 1 comment ·
-
external_created_at is no longer used for the message timestamp since the new message UI (v4.4.0) OpenBug Frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100