On Tuesday, January 17, 2012 2:22:26 pm Scott Long wrote:
> On Jan 17, 2012, at 8:08 AM, John Baldwin wrote:
> > On Sunday, January 15, 2012 6:32:43 pm Colin Percival wrote:
> >> On 01/15/12 15:28, John Baldwin wrote:
> >>> On 1/15/12 2:09 AM, Eitan Adler wrote:
> Log:
> - Fix undefined
On Jan 17, 2012, at 8:08 AM, John Baldwin wrote:
> On Sunday, January 15, 2012 6:32:43 pm Colin Percival wrote:
>> On 01/15/12 15:28, John Baldwin wrote:
>>> On 1/15/12 2:09 AM, Eitan Adler wrote:
Log:
- Fix undefined behavior when device_get_name is null
- Make error message more
On 01/17/2012 10:48, John Baldwin wrote:
> On Tuesday, January 17, 2012 12:29:06 pm Andriy Gapon wrote:
>> on 17/01/2012 19:12 Eitan Adler said the following:
>>> To me seeing "(null)" from the output of printf indicates "There is a
>>> bug here, printf should never be given a NULL argument.".
>>>
On Tuesday, January 17, 2012 12:29:06 pm Andriy Gapon wrote:
> on 17/01/2012 19:12 Eitan Adler said the following:
> > To me seeing "(null)" from the output of printf indicates "There is a
> > bug here, printf should never be given a NULL argument.".
> > However, given that it isn't undefined here,
on 17/01/2012 19:12 Eitan Adler said the following:
> To me seeing "(null)" from the output of printf indicates "There is a
> bug here, printf should never be given a NULL argument.".
> However, given that it isn't undefined here, and the objections I've
> received I will revert this part of the ch
On Tue, Jan 17, 2012 at 10:08 AM, John Baldwin wrote:
> On Sunday, January 15, 2012 6:32:43 pm Colin Percival wrote:
>> On 01/15/12 15:28, John Baldwin wrote:
>> > On 1/15/12 2:09 AM, Eitan Adler wrote:
>> >> Log:
>> >> - Fix undefined behavior when device_get_name is null
>> >> - Make error
On Sunday, January 15, 2012 6:32:43 pm Colin Percival wrote:
> On 01/15/12 15:28, John Baldwin wrote:
> > On 1/15/12 2:09 AM, Eitan Adler wrote:
> >> Log:
> >>- Fix undefined behavior when device_get_name is null
> >>- Make error message more informative
> >
> > The in-kernel printf(9) alw
On 01/15/12 15:28, John Baldwin wrote:
> On 1/15/12 2:09 AM, Eitan Adler wrote:
>> Log:
>>- Fix undefined behavior when device_get_name is null
>>- Make error message more informative
>
> The in-kernel printf(9) always prints "(null)" for %s when the pointer is
> NULL,
> so that wasn't un
On 1/15/12 2:09 AM, Eitan Adler wrote:
Author: eadler (ports committer)
Date: Sun Jan 15 07:09:18 2012
New Revision: 230125
URL: http://svn.freebsd.org/changeset/base/230125
Log:
- Fix undefined behavior when device_get_name is null
- Make error message more informative
The in-kernel pri
Author: eadler (ports committer)
Date: Sun Jan 15 07:09:18 2012
New Revision: 230125
URL: http://svn.freebsd.org/changeset/base/230125
Log:
- Fix undefined behavior when device_get_name is null
- Make error message more informative
PR: kern/149800
Submitted by: olgeni
Approv
10 matches
Mail list logo