[ruby-core:122610] [Ruby Feature#21454] "undefined method 'break' for an instance of Binding"
Issue #21454 has been reported by vo.x (Vit Ondruch). ---------------------------------------- Feature #21454: "undefined method 'break' for an instance of Binding" https://bugs.ruby-lang.org/issues/21454 * Author: vo.x (Vit Ondruch) * Status: Open ---------------------------------------- Running my code with `rdbg` and using `binding.break`, it is a bit unfortunate that subsequently running the code without `rdbg`, it fails with error such as: ~~~ NoMethodError: undefined method 'break' for an instance of Binding ~~~ Could this method become no-op if the `rdbg` is not loaded? If there was some concern about this, then it could print some helpful warning or what not. -- https://bugs.ruby-lang.org/
Issue #21454 has been updated by nobu (Nobuyoshi Nakada). Use no-dbg.rb with `RUBYOPT=-rno-dbg` when you run without `rdbg`. ```ruby class Binding def break = nil end ``` ---------------------------------------- Feature #21454: "undefined method 'break' for an instance of Binding" https://bugs.ruby-lang.org/issues/21454#change-113992 * Author: vo.x (Vit Ondruch) * Status: Open ---------------------------------------- Running my code with `rdbg` and using `binding.break`, it is a bit unfortunate that subsequently running the code without `rdbg`, it fails with error such as: ~~~ NoMethodError: undefined method 'break' for an instance of Binding ~~~ Could this method become no-op if the `rdbg` is not loaded? If there was some concern about this, then it could print some helpful warning or what not. -- https://bugs.ruby-lang.org/
Issue #21454 has been updated by ko1 (Koichi Sasada). Status changed from Open to Feedback In today's dev meeting, we emphasized that it's important to ensure `binding.break` (or `debugger`) is removed before release, so having it as a no-op is a bad idea. ---- BTW debug.gem supports specifying breakpoints by adding environment variables for example, and you can ignore them without `rdbg`. However, specifying file and line number is tough, so I think good editor supports makes it better. ---------------------------------------- Feature #21454: "undefined method 'break' for an instance of Binding" https://bugs.ruby-lang.org/issues/21454#change-113993 * Author: vo.x (Vit Ondruch) * Status: Feedback ---------------------------------------- Running my code with `rdbg` and using `binding.break`, it is a bit unfortunate that subsequently running the code without `rdbg`, it fails with error such as: ~~~ NoMethodError: undefined method 'break' for an instance of Binding ~~~ Could this method become no-op if the `rdbg` is not loaded? If there was some concern about this, then it could print some helpful warning or what not. -- https://bugs.ruby-lang.org/
Issue #21454 has been updated by vo.x (Vit Ondruch). nobu (Nobuyoshi Nakada) wrote in #note-1:
Use no-dbg.rb with `RUBYOPT=-rno-dbg` when you run without `rdbg`.
```ruby class Binding def break = nil end ```
Interesting idea. Assuming that I should request this feature in rdbg project.
BTW debug.gem supports specifying breakpoints by adding environment variables for example, and you can ignore them without rdbg.
Sorry, could you please elaborate? Maybe share some example? ---------------------------------------- Feature #21454: "undefined method 'break' for an instance of Binding" https://bugs.ruby-lang.org/issues/21454#change-113996 * Author: vo.x (Vit Ondruch) * Status: Feedback ---------------------------------------- Running my code with `rdbg` and using `binding.break`, it is a bit unfortunate that subsequently running the code without `rdbg`, it fails with error such as: ~~~ NoMethodError: undefined method 'break' for an instance of Binding ~~~ Could this method become no-op if the `rdbg` is not loaded? If there was some concern about this, then it could print some helpful warning or what not. -- https://bugs.ruby-lang.org/
participants (3)
-
ko1 (Koichi Sasada) -
nobu (Nobuyoshi Nakada)
-
vo.x (Vit Ondruch)