|
From: Darren B. <dar...@ad...> - 2005-05-22 21:14:44
|
Thanks for the idea, Nicolas. I checked a couple of the GUIs and in the two I checked, they seem to be simply hunting for the text of the error messages. If the phrasing of the message were changed, then these tools would break, of course. Also, they'll miss any new error conditions that get added. That's another reason why a marker in the output stream, such as "ERROR", would be useful. The --xml=yes feature sounds like it might make this easier. It might make more sense to change the syntax to --log-format=xml, so that other formats could be added later. The default for this would be something like --log-format=plain (the current output). And in fact for a machine-readable output, --log-format=raw could produce ONLY error messages. This is just speculation, and food for thought. Thanks for the input. DB -----Original Message----- From: Nicholas Nethercote Sent: Saturday, May 21, 2005 3:30 PM To: Darren Burns Subject: Re: [Valgrind-users] Parsing the output file On Fri, 20 May 2005, Darren Burns wrote: > But it's hard for a program to pick out these errors because they're > just text amongst other text. Is there (or could there be) an option > to make these errors easier to parse out? I couldn't find any. Julian just added a --xml=yes option to the 3.0 repository at valgrind.org. Note that it's just been added, and could well change in the future. Also, you could look at how the GUIs such as Alleyoop and Valgui parse the output. N |