|
From: Darren B. <dar...@ad...> - 2005-05-21 02:44:21
|
Hi, The "commentary" output is human-readable, but I'm thinking about automatically detecting and reporting memory errors in our test suite that runs every night. Currently the output is something like: ==19346== ==19346== Conditional jump or move depends on uninitialised value(s) 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. For example ==19346== ==19346== [ERROR #12345] Conditional jump or move depends on uninitialised value(s) or perhaps ==19346== ==19346== [BEGIN ERROR #12345] ==19346== Conditional jump or move depends on uninitialised value(s) ... ==19346== [END ERROR #12345] (where 12345 is the unique numeric code that corresponds to the "Condition jump" error in this case). Thanks, DB |
|
From: Nicholas N. <nj...@cs...> - 2005-05-21 19:29:59
|
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 |
|
From: Jeffrey S. <fe...@no...> - 2005-05-22 23:44:26
|
On Fri, 2005-05-20 at 19:44 -0700, Darren Burns wrote: > Hi, > > The "commentary" output is human-readable, but I'm thinking about > automatically detecting and reporting memory errors in our test suite > that runs every night. > > Currently the output is something like: > > ==19346== > ==19346== Conditional jump or move depends on uninitialised value(s) > > 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. > > For example > > ==19346== > ==19346== [ERROR #12345] Conditional jump or move depends on > uninitialised value(s) > > or perhaps > > ==19346== > ==19346== [BEGIN ERROR #12345] > ==19346== Conditional jump or move depends on uninitialised value(s) > ... > ==19346== [END ERROR #12345] it already works very similarly to this now ==<pid>==SPACEThread: <thread id> ==<pid>==SPACE<error> ==<pid>==SPACE SPACE SPACE...<details> ==<pid>==SPACE SPACE SPACE...<details> ==<pid>== note that "blank" lines will end a report and that the error details are indented farther than the error (not that it even needs to be in order to be parseable since we know the first line is the error anyway) I'll agree that a more machine parseable format would be nice, but it's not really necessary to do what you want. Jeff |