boblq wrote:
How does this work for compiled code? Or is this simply something
one uses for interpreted code?
I think that Visual Studio does this as well using debugging traps. It
compiles the code in the background and then patches it in during
debugging.
He,he. Do you really use that?
Surprisingly, yes.
I can wind up with data sets which can take quite a while to load, sort,
modify, etc. Not having to restart because some null pointer popped an
exception is good for debugging efficiency.
Also, I sometimes wind up with systems which are network state
sensitive. This means that I may get one-off conditions which will be
hard to reproduce again.
Granted, I am going to rerun this from scratch when I am done, but it
definitely saves me time under debugging.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
