|
From: David J. B. <dba...@co...> - 2005-12-14 21:34:19
|
Is there a diocument that explains each message you might see from valgrind? I found documentation ofr most errors and some warnings but not for some of the verbose output like: ==2799== TRANSLATE: 0x8C971E redirected to 0x3414F198 |
|
From: Nicholas N. <nj...@cs...> - 2005-12-14 21:54:43
|
On Wed, 14 Dec 2005, David J. Bakeman wrote: > Is there a diocument that explains each message you might see from valgrind? > > I found documentation ofr most errors and some warnings but not for some of > the verbose output like: > > ==2799== TRANSLATE: 0x8C971E redirected to 0x3414F198 It's an internal detail of little interest to users. Most of the messages with -v are like this (eg. various internal stats we use for performance analysis), I think only the error counts are of obvious interest. This came up a few times in the recent survey, so perhaps we'll separate the verbose messages that are interesting to users from those that are only interesting to developers. Nick |
|
From: Dennis L. <pla...@tz...> - 2005-12-14 22:32:53
|
Am Mittwoch, den 14.12.2005, 15:54 -0600 schrieb Nicholas Nethercote: > It's an internal detail of little interest to users. Most of the messages > with -v are like this (eg. various internal stats we use for performance > analysis), I think only the error counts are of obvious interest. This > came up a few times in the recent survey, so perhaps we'll separate the > verbose messages that are interesting to users from those that are only > interesting to developers. Thats a great idea. Maybe even with kind of debug levels so -v -vv -vvv -vvvv give increasingly more output? greets Dennis |