Re: qconf handling NULL pointers
Hi, On Saturday 06 January 2007 12:44, Cyrill V. Gorcunov wrote: > I found qconf have a few malloc(), strdup() without any check for NULL > returned code. May be it should be fixed? Am I wrong? The code isn't really supposed to deal with it, at most they could be replaced with a variant that prints an error message and exits. bye, Roman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
qconf handling NULL pointers
Hi, Roman I found qconf have a few malloc(), strdup() without any check for NULL returned code. May be it should be fixed? Am I wrong? -- - Cyrill - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
qconf handling NULL pointers
Hi, Roman I found qconf have a few malloc(), strdup() without any check for NULL returned code. May be it should be fixed? Am I wrong? -- - Cyrill - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: qconf handling NULL pointers
Hi, On Saturday 06 January 2007 12:44, Cyrill V. Gorcunov wrote: I found qconf have a few malloc(), strdup() without any check for NULL returned code. May be it should be fixed? Am I wrong? The code isn't really supposed to deal with it, at most they could be replaced with a variant that prints an error message and exits. bye, Roman - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
