|
|
|
[
Permlink
| « Hide
]
Chris Williams - 08/Nov/07 01:14 PM
Well I can modify the code to allow trying to set multiple exceptions, but after testing that it seems we're bumping into something else that is limiting to one - and unfortunately I think that may be the debugging libraries themselves.
Pushing to 1.1.0 relse plan since this requires ruby-debug supporting multiple exceptions.
This is an enhancement and therefore shouldn't be targeted at a bugfix release stream. At best it will get targeted for the next major release, which is 1.2.0.
Looks like as of ruby-debug-base 0.10.1 it now supports multiple exception breakpoints (http://rubyforge.org/frs/shownotes.php?release_id=21031
But in looking at ruby-debug-base code, and ruby-debug-ide, there's actually no way to turn an exception breakpoint off any more! I'm sending out an e-mail to Rocky who works on ruby-debug to see if I'm missing something or that needs to be added back into ruby-debug itself. Integrated in
rdt #63partial implementation of - Allow multiple exception breakpoints and break on any exception. Now we support adding multiple breakpoints. The issue is that if the user is using classic debugger this will get confusing since that only handles one (but hopefully they won't be using it). The other issue is that we now have to basically "disable" removing exception breakpoints in ruby-debug since the command to get rid of them no longer exists! Implemented, with the caveat of no longer being able to disable exception breakpoints (see
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||