|
From: Jeffrey S. <fe...@no...> - 2006-06-12 21:33:58
|
I just noticed the timestamp format changed somewhere between Valgrind 2.4.0 and Valgrind 3.1.0 in the non-xml log output. The new date format looks like "##:##:##:##.###" Can anyone tell me what each of these fields are and when the change was made? (was it made in 3.0? or just in 3.1?) Thanks, -- Jeffrey Stedfast Evolution Hacker - Novell, Inc. fe...@no... - www.novell.com |
|
From: Nicholas N. <nj...@cs...> - 2006-06-12 23:20:24
|
On Mon, 12 Jun 2006, Jeffrey Stedfast wrote: > I just noticed the timestamp format changed somewhere between Valgrind > 2.4.0 and Valgrind 3.1.0 in the non-xml log output. > > The new date format looks like "##:##:##:##.###" > > Can anyone tell me what each of these fields are and when the change was > made? (was it made in 3.0? or just in 3.1?) The release notes say it changed in 3.1.0: - The --time-stamp option no longer gives an absolute date and time. It now prints the time elapsed since the program began. The manual (section 2.6.2) explains the meaning of the fields. Nick |
|
From: Jeffrey S. <fe...@no...> - 2006-06-13 14:09:33
|
On Tue, 2006-06-13 at 09:20 +1000, Nicholas Nethercote wrote: > On Mon, 12 Jun 2006, Jeffrey Stedfast wrote: > > > I just noticed the timestamp format changed somewhere between Valgrind > > 2.4.0 and Valgrind 3.1.0 in the non-xml log output. > > > > The new date format looks like "##:##:##:##.###" > > > > Can anyone tell me what each of these fields are and when the change was > > made? (was it made in 3.0? or just in 3.1?) > > The release notes say it changed in 3.1.0: > > - The --time-stamp option no longer gives an absolute date and time. > It now prints the time elapsed since the program began. > > The manual (section 2.6.2) explains the meaning of the fields. Thanks! I somehow missed it when skimming the manual earlier... Jeff > > Nick -- Jeffrey Stedfast Evolution Hacker - Novell, Inc. fe...@no... - www.novell.com |