malloc fails if the function is called twice, how?

[Novice]

When Main calls a function, which has a couple of malloc() statements, and
their corresponding free() statements, why did it crash?

How should I fix this problem?

TIA

[Ian Collins]

Novice wrote:

When Main calls a function, which has a couple of malloc() statements, and
their corresponding free() statements, why did it crash?

How should I fix this problem?

Show the code! There could be any number of reasons.

--
Ian Collins.

[Rolf Magnus]

Novice wrote:

When Main calls a function, which has a couple of malloc() statements, and
their corresponding free() statements, why did it crash?
Probably because you made an error.
How should I fix this problem?

By removing the error.

[John Carson]

"Novice" <no****@novice. com> wrote in message
news:e4******** **@mawar.singne t.com.sg

When Main calls a function, which has a couple of malloc()
statements, and their corresponding free() statements, why did it
crash?
How should I fix this problem?

TIA

The problem is on line 47 of your code.

--
John Carson

[Ron Natalie]

Novice wrote:

When Main calls a function, which has a couple of malloc() statements, and
their corresponding free() statements, why did it crash?

How should I fix this problem?

Look carefully. Crashes in malloc/free are a result of some undefined
behavior corrupting the malloc internal tables. Most likely reasons
are:

1. Freeing a value not directly obtained from malloc.

char* x = static_cast<cha r*>(malloc(10)) ;
x++;
free(x);

or

char x;
free(&x);

2. Freeing a value twice.

void* p = malloc(20);
free(p);
free(p);

3. Writing off the end of a malloc'd bloc

char* x = static_cast<cha r*>(malloc(4));
strcpy(x, "abcd");

Some compilers have debug tools built in to help you troubleshoot this
and there are some external third party tools available. However,
usually so serious introspection of your code will help.

Frankly, if you are a new C++ programmer (or perhaps even an old one),
the fact that you are messing with malloc at all means you have serious
problems in your design approach.

[Martin Jørgensen]

Novice wrote:

When Main calls a function, which has a couple of malloc() statements, and
their corresponding free() statements, why did it crash?

How should I fix this problem?

1) Delete your code completely and the error disappears.

2) You could also just change it to:

#include <iostream>
using namespace std;

int main()
{
cout << "Hi Mom! My memory allocation error disappeared now!!!\n";
return 0;
}
Best regards / Med venlig hilsen
Martin Jørgensen

--
---------------------------------------------------------------------------
Home of Martin Jørgensen - http://www.martinjoergensen.dk

[frankgerlach]

I am suprised none of the responding people mentioned the use of a
memory checker such as Purify (www.ibm.com, trial version available) or
valgrind. The latter is a free tool and very valuable when debugging
memory problems.

[Victor Bazarov]

fr**********@gm ail.com wrote:

I am suprised none of the responding people mentioned the use of a
memory checker such as Purify (www.ibm.com, trial version available)
or valgrind. The latter is a free tool and very valuable when
debugging memory problems.

....unless your problems are on Windows or any other platform where it
is not available. Generally speaking, _if_ tools exist, use it. But
what if it doesn't? Perhaps that's why people here refrain from giving
platform-specific product recommendations .

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask