On March 18, 2015 11:44:50 AM GMT+01:00, Zhiqiang Zhang
zhangzhiqiang.zh...@huawei.com wrote:
For some rarely cases(almost App bugs), calling malloc with
a very largre size, checked_request2size check will fail,set
ENOMEM, and return 0 to caller.
But this will let __malloc_lock futex locked and
For some rarely cases(almost App bugs), calling malloc with
a very largre size, checked_request2size check will fail,set
ENOMEM, and return 0 to caller.
But this will let __malloc_lock futex locked and owned by the
caller. In multithread circumstance, other thread calling
malloc/calloc will NOT
On Wed, Mar 18, 2015 at 12:05:12PM +0100, Bernhard Reutner-Fischer wrote:
On March 18, 2015 11:44:50 AM GMT+01:00, Zhiqiang Zhang
zhangzhiqiang.zh...@huawei.com wrote:
For some rarely cases(almost App bugs), calling malloc with
a very largre size, checked_request2size check will fail,set
