Segmentation fault when a custom chunk allocator returns a memory block larger than the chunk size

[meng]

Hi, guys, I verified that silly bug is the cause. Replacing it with 1<<22
makes everything fine :)


On Wed, Jul 30, 2014 at 8:03 PM, Rogier 'DocWilco' Mulhuijzen <
rogier+jemalloc at fastly.com> wrote:

> Yeah, ^ is bitwise XOR, not power. :)
>
> On Mon, Jul 28, 2014 at 7:02 PM, Bradley C. Kuszmaul <bradley at mit.edu>
> wrote:
>
>> Also 2^31 == 29, not 1<<31
>>
>>
>>


-- 
Best
-Xiaoqiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jemalloc.net/mailman/jemalloc-discuss/attachments/20140730/2db88678/attachment.html>