On Saturday 03 December 2005 05:18 pm, Andrew Lentvorski wrote: > 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.
Yeh. This sounds like the point. You work with all of this monster big data, big program VLSI design stuff. So anything that makes any of it more interactive is a "good thing." Is this the driver? Or am I hallucinating about your context? > 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. Ugly. Sop you can use the patch and run to test against the same rare occurrence? > Granted, I am going to rerun this from scratch when I am done, but it > definitely saves me time under debugging. Got it. BobLQ > -a -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
