Hi, Adam Thanks for the hint. Do you mean this functionality is/will be deprecated?
Actually, I did some experiments with hardware watchpoint yesterday, not using Dtrace, but the /proc filesystem in OpenSolaris. It seemed to work though. As I am not doing a commercial application, just a data analysis for my academic research project. The RFE issue might not be very important. However, I do have a doubt about watchpoint. So, everytime memory is accessed, a hardware trap signal is sent to the application, right? What if there are multiple threads accessing memory concurrently? In my understanding, signal handling is a block operation, so the threads should be blocked and then resumed execution after the trap is handled, correct? Will this in effect serialize the threads? If yes, there is not so much difference than merely using Valgrind, etc. Thanks Peng Du 02/16/2009 On Sun, 2009-02-15 at 19:38 -0800, Adam Leventhal wrote: > Hi Peng, > > You can't do this today with DTrace though a watchpoint provider has > been a long-standing RFE (that's I'd love to get to soon!). For now > your best bet is mdb. > > Adam > > On Feb 13, 2009, at 9:34 AM, Peng Du wrote: > > > Hello, everyone > > > > I am a newbie of DTrace and OpenSolaris. Just wondering is it possible > > to trace every memory read/write of a specific process given the pid? > > Basically speaking, I want to record the virtual addresses being > > accessed by the process, using which I will try to do some online > > analysis. > > > > If DTrace does not support this type of instrumentation, will other > > tools in OpenSolaris help me achieve that, such as mdb, and etc? > > > > Thanks! > > > > Peng Du > > Feb 12, 2009 > > > > _______________________________________________ > > dtrace-discuss mailing list > > dtrace-discuss@opensolaris.org > > > -- > Adam Leventhal, Fishworks http://blogs.sun.com/ahl _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
