Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
bug in heap command #568
Bug of command heap
Steps to reproduce
This bug is due to a strange alignment strategy in newer version of 32 bit glibc.
In a nutshell, the first 16 bytes of heap is 0 in glibc-2.26 (32bit), glibc-2.27 (32bit).
As a result, while parsing heap, the first chunk has size 0 and trigger stop.
No need for setup, just check those two glibc.
fix is really easy, just ignore the first chunk if size is 0.
I believe the reason of this is thread cache and that a lot of bytes in there belong to