|
From: Dennis L. <pla...@in...> - 2005-08-11 14:17:05
|
Am Donnerstag, den 11.08.2005, 08:29 -0500 schrieb Nicholas Nethercote: > On Thu, 11 Aug 2005, Dennis Lubert wrote: > > > Running valgrind3 with -v produces also for invalid file descriptor > > warnings a stacktrace > > This question has been asked twice recently. Perhaps we should print the > stack trace by default? Or upgrade these warnings to full error messages > so dups aren't shown, they can be suppressed, etc? > > N I think that usually errors reported by valgrind are "serious programming errors" that should be fixed, rather than suppressed whenever possible. But passing a negative value to write/read etc. isnt that serious, since at this point the function directly reports EBADF via errno, and I think in some programs its quite common to (more or less accidently) pass invalid fds (theyre checked only now and then, maybe in between set by another thread to -1) Maybe there should be a switch like "--full-stack-trace" that shows at every possible occasion every stacktrace that can be printed, also the usual ones without limitation... greets Dennis |