dev-cpp-users

Re: [Dev-C++] q??

[<Met...@ao...>]

Hi Senem

Zodiaq is joking with memory leaks...

In fact, that means that the memory is not handled the way it should be 
inside a program. 

It can be a single pointer allocated twice, allocated memory not freed...

Some proggys are very leaky. Like AOL for example. I wonder if the people 
that coded that piece of sh** ever heard of the "free" instruction in C 
standard library.

Kind regards

--

Seb

Re: [Dev-C++] q??

[<ste...@ge...>]

How is it possible to be sure if your program is not leaking any memory? =
Is there anyway to test a program for leaks?

thanks

     Stein Nyg=E5rd - http://steinware.dk
lapido, ergo sum
  ----- Original Message -----=20
  From: Met...@ao...=20
  To: dev...@li...=20
  Sent: Sunday, September 01, 2002 8:22 PM
  Subject: Re: [Dev-C++] q??


  Hi Senem=20

  Zodiaq is joking with memory leaks...=20

  In fact, that means that the memory is not handled the way it should =
be inside a program.=20

  It can be a single pointer allocated twice, allocated memory not =
freed...=20

  Some proggys are very leaky. Like AOL for example. I wonder if the =
people that coded that piece of sh** ever heard of the "free" =
instruction in C standard library.=20

  Kind regards=20

  --=20

  Seb=20

Re[2]: [Dev-C++] q??

[Zodiaq <zo...@ac...>]

Hello Stein and all Dev-C++ users,

Sunday, September 1, 2002, 9:09:20 PM, Stein wrote as follows:

SN> How is it possible to be sure if your program is not leaking any memory? Is there anyway to test a program for leaks?

I think the goood idea is to use own containers that checks at program
termination that all prevoiusly acquired memory is properly fried...
well, to do that 'just' overwrite the new keyword... everywthing is
Brue Eckel's "Thinking in C++", just check: http://64.78.49.204/
-- 
regards, Zodiaq

Re: [Dev-C++] q??

[Elizabeth B. <sog...@ya...>]

Stein Nyg=E5rd <ste...@ge...> writes:

> How is it possible to be sure if your program is not leaking any
> memory? Is there anyway to test a program for leaks?

There are various programs and libraries that help one keep track of
this sort of thing.

An email just came in and mentioned BoundsChecker:

<http://www.compuware.com/products/devpartner/bounds/>

There is also electric fence (efence) but I am not sure whether or not
that has been ported to mingw.

You may want to review this:

<http://netlib.bell-labs.com/cm/cs/cstr/123.ps.gz>

IIRC it contains a good primer pointers (found at:
<http://www.lysator.liu.se/c/c-www.html> ; contains general C info)

Elizabeth

RE: [Dev-C++] q??

[Ioannis V. <no...@ho...>]

Memory leak is when you allocate memory dynamically (on the free store) =
and you do not free it. You can avoid memory leak by using the standard =
containers instead of allocating and deallocating memory dynamically.
=20
=20
For example
=20
=20
Instead of writing:
=20
class A
{
 int *p;
// ...
 public:
A(const int x) { p=3Dnew int [x]; }
~A() { delete[] p; }
// ...
};
=20
=20
write
=20
class A
{
 vector v;
// ...
public:=20
A(const int x):v(x) {}
// ...
=20
=20
Instead of writing
=20
=20
int *something()
{
 //...=20
  int *p=3Dnew int[20];
 //...
=20
return p;
}
=20
=20
write
=20
void something(vector<int>&v)
{
 // store everything in v;
}
=20
=20
When the container reaches the end of its scope, it clears itself =
automatically.
=20
=20
=20
=20
Ioannis

* Ioannis Vranos
* Programming pages: http://www.noicys.cjb.net =
<http://www.noicys.cjb.net/>=20
* Alternative URL: http://run.to/noicys

-----Original Message-----
From: dev...@li... =
[mailto:dev...@li...] On Behalf Of Stein =
Nyg=CE=B5rd
Sent: Sunday, September 01, 2002 10:09 PM
To: Met...@ao...; dev...@li...
Subject: Re: [Dev-C++] q??


How is it possible to be sure if your program is not leaking any memory? =
Is there anyway to test a program for leaks?
=20
thanks

     Stein Nyg=C3=A5rd - http://steinware.dk
lapido, ergo sum

----- Original Message -----=20
From: Met...@ao...=20
To: dev...@li...=20
Sent: Sunday, September 01, 2002 8:22 PM
Subject: Re: [Dev-C++] q??

Hi Senem=20

Zodiaq is joking with memory leaks...=20

In fact, that means that the memory is not handled the way it should be =
inside a program.=20

It can be a single pointer allocated twice, allocated memory not =
freed...=20

Some proggys are very leaky. Like AOL for example. I wonder if the =
people that coded that piece of sh** ever heard of the "free" =
instruction in C standard library.=20

Kind regards=20

--=20

Seb=20