Re: svn commit: r309194 - head/usr.sbin/syslogd

2016-11-27 Thread Ryan Stone
> > There is something very wrong in the code here. nextp is never > initialized, so obviously we can't access *nextp. I'm surprised that this > code can even compile with -Werror. I'd fix it but it'd not clear to me > what nextp is intended to do. > Apologies for the noise; I didn't see

Re: svn commit: r309194 - head/usr.sbin/syslogd

2016-11-27 Thread Ryan Stone
On Sat, Nov 26, 2016 at 10:50 AM, Baptiste Daroussin wrote: > Author: bapt > Date: Sat Nov 26 15:49:59 2016 > New Revision: 309194 > URL: https://svnweb.freebsd.org/changeset/base/309194 > > Log: > initialize *nextp which could be left uninitialized in case the >

Re: svn commit: r309194 - head/usr.sbin/syslogd

2016-11-27 Thread Raphael Kubo da Costa
Baptiste Daroussin writes: > Author: bapt > Date: Sat Nov 26 15:49:59 2016 > New Revision: 309194 > URL: https://svnweb.freebsd.org/changeset/base/309194 > > Log: > initialize *nextp which could be left uninitialized in case the > configuration > file cannot be open/read >

svn commit: r309194 - head/usr.sbin/syslogd

2016-11-26 Thread Baptiste Daroussin
Author: bapt Date: Sat Nov 26 15:49:59 2016 New Revision: 309194 URL: https://svnweb.freebsd.org/changeset/base/309194 Log: initialize *nextp which could be left uninitialized in case the configuration file cannot be open/read Reported by: Coverity via cem MFC after:2 days CID: