Trond Myklebust wrote: > On Thu, 2009-01-22 at 09:36 +1100, Greg Banks wrote: > >> Chuck Lever wrote: >> >>> >>> >> It depends on whether distros can be convinced to enable it by default, >> and install by default any necessary userspace infrastructure. The >> most important thing for field debugging is Just Knowing that you have >> all the bits necessary to perform useful debugging without having to >> find some RPM that matches the kernel that the machine is actually >> running now, and not the one that was present when the machine was >> installed. >> > > Which is precisely why dprintk() is such a bad choice as a basis for a > set of trace points: every new patch and bugfix that the distro applies > will result in a reshuffling of the trace points as code is cleaned up > and moved around or removed entirely. > Yes, if the filename and line number were the only information going out. The dprintk() format is usually enough (ignoring the patchy quality of the current dprintk set) to give a developer enough clue about which dprintk is which. Or am I missing something? -- Greg Banks, P.Engineer, SGI Australian Software Group. the brightly coloured sporks of revolution. I don't speak for SGI. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
