Perry The Cynic wrote: > Assigning to uregs[] (as per RFE 5005776) seems useful but much inferior > to assigning to arg* (or args[]). Why be architecture-specific when you > can be source-specific? > > On a more general note, being new to DTrace I read the "how I patched a > system call for an errant third party program" description and deduced > that "fixing" programs (not just observing how they fail :-) is one of > its design purposes. Am I mistaken, or is changing parameters/return > values just one of those things that hasn't been done yet (but lines up > properly with the intended use of the feature)?
I think you're wrong in deducing this. DTrace is first and foremost an observability tool; once you've found where a problem lies in a program/piece of code, you need to fix the code, not apply some kind of over-engineered band-aid*. Michael (*)lest I be misunderstood: I don't see DTrace as overengineered. Using it for "fixing" programgs would be. -- Michael Schuster Sun Microsystems, Inc. http://blogs.sun.com/recursion _______________________________________________ dtrace-discuss mailing list [email protected]
