On Mon, Nov 23, 2009 at 6:42 AM, Craig Small <[email protected]> wrote:
> The xcalloc is in the original code, I can even see it in the 3.2.7 > code. Yeah, I know. > So is the solution to test the result of the file2str on the status file > and if that fails set certain pointers to null? something like that, with likely/unlikely on the test -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
