Malloc calls the brk system call to actually get new memory blocks from the system, but it manages that memory itself, keeping a free list for future allocation. So that may or may not be helpful.
Does the program have a unique enough execname, that you can check that in the predicate rather than the pid? Or is there a unique call at the beginning, like an mmapped or opened file that you can use as a trigger? Chip > -----Original Message----- > From: dtrace-discuss-boun...@opensolaris.org [mailto:dtrace-discuss- > boun...@opensolaris.org] On Behalf Of Vladimir Kvashin > Sent: Monday, December 29, 2008 10:35 AM > To: dtrace-discuss@opensolaris.org > Subject: [dtrace-discuss] Is there any way to trace malloc without > using pidprovider? > > Hi, > > Is there any way to trace malloc without using pid provider? > > The issue is that the program we need to trace is a short-living one > and we don't know its pid at the time dtrace is launched; but we can > get this pid some moment later. > -- > This message posted from opensolaris.org > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss@opensolaris.org _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
