On 23.04.2009 01:28, Stefan Reinauer wrote: > On 23.04.2009 1:09 Uhr, Joseph Smith wrote: > >> On Wed, 22 Apr 2009 13:50:54 -0700, ron minnich <[email protected]> wrote: >> >> >>> On Tue, Apr 21, 2009 at 4:41 AM, Joseph Smith <[email protected]> >>> >>> >> 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 >> >> > > You can.. > > btw.. qa.coreboot.org holds logs of each revision too (the last few > 200-1000 depending when I clean up) > > http://qa.coreboot.org/log_buildbrd.php?revision=4187&device=ip1000&vendor=thomson&num=2 > > But please note that gcc does not catch all the tricky mistakes we make. >
Or you run cd util/abuild; abuild -t thomson/ip1000 and look at coreboot-builds/thomson_ip1000/make.log Regards, Carl-Daniel -- http://www.hailfinger.org/ -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
