From: Will C. <wc...@re...> - 2003-12-16 16:06:28
|
John Levon wrote: > On Tue, Dec 16, 2003 at 10:21:45AM -0500, Will Cohen wrote: > > >>Archiving OProfile data would be very useful. It would allow offline > > > This has been discussed before a little. > > There are a couple of problems with it.First, any archive is likely to > be pretty large, since you're effectively packaging the entire running > binary code set in the default OProfile mode. Yes, size certainly can be a problem. Maybe have "image:" and "image-exclude:" specifiers to limit what gets archived. One could tar up and compress the archive for storage; debugging information definitely compresses. There are situations where being able to archive data up so it can be analyzed/reviewed later else where is really, useful, e.g. data for an academic paper and data from a customer's system (which you do not have access to). > Second, this : > > >>"opreport" would have an additional specification parameter: >> >>archive:the_root_of_the_archive > > > would be somewhat painful: we can't even get binary: to work nicely with > the current libpp code. This is mainly used with modules? Or this being used as an "archive this one sample file and executable"? I will take a look at "binary:" and "sample-file:" -Will |