On Wed, 22 Apr 2009 13:50:54 -0700, ron minnich rminnich@gmail.com wrote:
On Tue, Apr 21, 2009 at 4:41 AM, Joseph Smith joe@settoplinux.org
wrote:
This really sounds like an unitialized variable or a bad pointer.
Wouldn't gcc catch these and error when building?
not always. that's what sparse can be useful for.
Why can't I just send the build output to a text file and then look through it for all the warnings/errors?
$ make > buildlog.txt