Just to clarify .. the intended use scenario is:
-q --xml=yes --log-file=/tmp/valgrind_myapp.pid%p
--xml-file=/tmp/valgrind_myapp.xml%p
That means:
* XML goes into /tmp/valgrind_myapp.xml%p
* the -q makes the normal output completely silent, unless there is
a critical error in Valgrind itself (eg, assertion failure, or
failure to read debug info from your executable)
Hence valgrind_myapp.pid%p should normally be empty. If it's not,
then it contains some critical error which the user should be made
aware of.
I think this is simple -- it means you don't have to do any
filtering/searching/analysis of valgrind_myapp.pid%p, you only
need to distinguish empty vs nonempty.
J
On Thursday 06 August 2009, Madhan Sadasivam wrote:
> It sure does Julian, I messed something for sure in my earlier trial.
>
> Thanks,
> Madhan.
>
> On Thu, Aug 6, 2009 at 2:42 PM, Julian Seward <[email protected]> wrote:
> > > I want the xml content to go to --xml-file and everything else
> > > to --log-file, the file names being different. Is there a way to do
> > > this.
> >
> > That's how it is supposed to work already!
> >
> > --xml=yes --log-file=/tmp/valgrind_myapp.pid%p
> > --xml-file=/tmp/valgrind_myapp.xml%p
> >
> > should do what you want.
> >
> > J
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
