> On Jan 7, 2020, at 6:52 AM, lijiazi <jqqlijiazi@xxxxxxxxx> wrote: > > If current object's memory is corrupted, there is a high > probability that next_objext stored in it will be rewritten as an > illegal value. It's better to check next_object this time than to > encounter a illegal pointer in next slub alloc like the following: I still have no answer for the previous question - how was current object’s memory corrupted?
