I get this error: “glibc detected”

Even if you’re not allocating memory directly, it happens under the hood in vector code and you most likely corrupted some portion of memory by writing where you are not supposed to. The most likely reasons I can think of are: Writing to an element that is out of bounds Using a pointer/reference to an element that … Read more

Understanding “corrupted size vs. prev_size” glibc error

OK, so I’ve managed to overcome this issue. First of all – A practical cause to “corrupted size vs. prev_size” is quite simple – memory chunk control structure fields in the adjacent following chunk are being overwritten due to out-of-bounds access by the code. if you allocate x bytes for pointer p but wind up writing beyond x in regards to … Read more