Mysterious malloc: sysmalloc: Assertion failed error

17,883

This usually happens when your code freed an invalid address at some prior time, or wrote past the end of the allocated memory block. Run your code through valgrind or some other memory profiler to see the point where this happens.

Share:
17,883

Related videos on Youtube

Ian
Author by

Ian

Updated on September 15, 2022

Comments

  • Ian
    Ian over 1 year

    I am getting a mysterious error and I have no idea why. This code runs several times before failing, and it always fails at the same point.

    Here is my code:

        assert(size > 0);
        int* sorted = malloc(size * sizeof(int));
    

    And here is the error I am getting when I run it:

        malloc.c:2369: sysmalloc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.
    

    I have tried printing out size and it is 1 in this case. This code runs several times with varying values of size, including 1, before failing.

    Does anyone have any idea what I am doing wrong?

    Thanks.

    • mah
      mah over 10 years
      @ouah I think that line is part of the malloc function itself, rather than part of the poster's code; he probably doesn't have the source to that library.
  • Ian
    Ian over 10 years
    I tried commenting out every time I used free. I still get the error.
  • Sergey Kalinichenko
    Sergey Kalinichenko over 10 years
    @Ian Then look for places where you allocate memory, and see if you always provide the correct sizeof, and also that the indexes into that memory are correct. This is the nastiest kind of errors, it's extremely hard to find them without a memory profiler.
  • Ian
    Ian over 10 years
    I tried running the code through valgrind and I found some mistakes. I will try fixing them to see if the error goes away. Thanks!
  • Ian
    Ian over 10 years
    That was it! I was reading outside of memory which caused me to later write outside of memory.