Glibc detected malloc() memory corruption (0xb6179bb8) when calling new keyword C++

Question

My program runs to a point where calling the new keyword would cause the error stated above. i.e. char* a = new char[100]. The error is reproducible and every time. I run the program until that point of calling the new keyword. It seems to be the memory location is corrupted at the point, but I'm not sure what he issue is.

What are the possible causes for this error?

The cause of the error is that you are doing something incorrect in your code. Since you haven't posted any code, it's impossible to be any more specific than that. — James McNellis
– James McNellis, Commented Oct 1, 2010 at 5:05
look at the previous memory allocation in your code, may be something wrong with that. Or you might corrupt the heap writing to the inappropriate address before your allocation. — Roman Shapovalov
– Roman Shapovalov, Commented Oct 1, 2010 at 5:40
0xb6179bb8 was it...? Just let me look that one up in my Big Book of Errors. More seriously - it's most likely to be another error with heap memory usage: deleting/freeing memory multiple times, mismatching single-var and array new/delete, overwriting memory before or after the memory blocks you've been reserving, but could be any other kind of behaviour that can cause undefined behaviour. You can typically use tools like valgrind or purify to find the point where you make some illegal operation causing this.... — Tony Delroy
– Tony Delroy, Commented Oct 1, 2010 at 6:06

Bart van Ingen Schenau · Accepted Answer · 2010-10-01 13:02:42Z

10

This error means that you have corrupted the bookkeeping data of the system memory manager. Such corruptions are typically the result of incorrect use of pointers, such as

Using an uninitialised pointer
Using a pointer after the memory it refers to has been freed (the freeing could have happened through another pointer)
Writing outside your array bounds

answered Oct 1, 2010 at 13:02

Bart van Ingen Schenau

15.9k4 gold badges34 silver badges42 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Glibc detected malloc() memory corruption (0xb6179bb8) when calling new keyword C++

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related