Two questions:
- Can explicit breakpoints be leveraged to incrementally patch fixes/changes
into a running app (during debugging)
- Can it be extended to take an external interrupt of some kind and enter a
breakpoint?
So far breakpoint has made my working in JEdit without a debugger pretty
bearable ! thanks a whole bunch, gavin!!
[does anyone have jedit working with ruby debugging?]
itsme213 wrote:
Two questions:
- Can explicit breakpoints be leveraged to incrementally patch fixes/changes
into a running app (during debugging)
Sure thing, after all you have a full-fledged irb shell and you can replace methods using it.
- Can it be extended to take an external interrupt of some kind and enter a
breakpoint?
Yup, though it will be a bit harder to get it to run in a specific context. I guess something like trap("SIGUSR1") { breakpoint } might do the trick.
Florian answered these, but were you thinking of any particular way
dev-utils could be enhanced?
Gavin
On Wednesday, November 17, 2004, 2:43:18 AM, itsme213 wrote:
Two questions:
- Can explicit breakpoints be leveraged to incrementally patch fixes/changes
into a running app (during debugging)
- Can it be extended to take an external interrupt of some kind and enter a
breakpoint?
Florian answered these, but were you thinking of any particular way
dev-utils could be enhanced?
Being able to interrupt a running program and drop into an irb/breakpoint
session would be nice.
Even nicer would be to have a mode whose possible values include
DBG_ON_BREAKPOINT: in that mode the "breakpoint" (whether hand-inserted or
by interrupt) drops into a ruby debugger session, not just irb. Any chance
of that?