malloc returned null pointer

[Jakob Clausen]

Hi.

I get the following error, when running the tests

test/LocalSocketTest.cpp:117: error: Failure in TEST(LocalSocketServer_systemtest, string)
src/CppUTest/TestMemoryAllocator.cpp:37: error:
    malloc returned null pointer

terminate called after throwing an instance of 'CppUTestFailedException'
Stack trace (most recent call last) in thread 7947:

This does not happen every time I run the tests - only about one fifth of the testruns fails in this way.

If I look at the stacktrace, then it looks like what is failing me is this function:

void SocketCommunication::newBufferSize(uint64_t size)
{
    if (size > totalSize)
    {
        totalSize = size;
        delete[] buffer;
        buffer = new char[totalSize];
    }
}

As the error is with malloc - I assume that it is new, that is failing me.

What could make malloc fail in this way?

I don't think I am out of memory.

Jakob.

[Bas Vodde]

Is it multi-threaded code?

Bas

--
You received this message because you are subscribed to the Google Groups "cpputest" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cpputest+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cpputest/20fbd9e2-e244-4297-949a-b580a26d71d1n%40googlegroups.com.

[Jakob Clausen]

Yes it is.

[Bas Vodde]

Hi,

Then you might want to try:

MemoryLeakWarningPlugin::turnOnThreadSafeNewDeleteOverloads on your main and see if that makes a difference.

Thanks!

Bas

To view this discussion on the web visit https://groups.google.com/d/msgid/cpputest/06f26407-190d-46c2-9343-b222c73ae7d4n%40googlegroups.com.

[Jakob Clausen]

That looks like a very good idea. :-)

I guess I always would want that, when I go multithreaded?

It looks good.

I will test some more.

[Jakob Clausen]

That seemed to do it.

Thank you very much.