Testing malloc results for null on the 400 (was: HTTP Authentication / base64 encoder?) -- C400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: [C400-L] Testing malloc results for null on the 400 (was: HTTP Authentication / base64 encoder?)
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 28 Aug 2003 14:04:15 -0500
Cc:
List-archive: <http://archive.midrange.com/c400-l>
List-help: <mailto:c400-l-request@midrange.com?subject=help>
List-id: C programming iSeries / AS400 <c400-l.midrange.com>
List-post: <mailto:c400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/c400-l>, <mailto:c400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/c400-l>, <mailto:c400-l-request@midrange.com?subject=unsubscribe>

Folks:

How critical is that the results of a malloc operation be tested for null on the 400?

I'm not allocating a huge amount of data.

The base64 code I adapted invoked some error handling routine if the malloc returned a null. I commented that line out, and it seems to work fine... but is this something I have to seriously be concerned about?

How often will a malloc of a small amount of memory fail on the 400?

Thanks!

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Testing malloc results for null on the 400 (was: HTTP Authentication / base64 encoder?) , Bob Crothers

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.