malloc and free

hi

routine xyz uses malloc and free functions. it gives
accurate and correct result if called once.

but if the function is called in a loop N number of
times then probably it gives segmentation fault.

what is the reason? can any body guess or test code
is needed?

thanks

ankit jain

____________________________________________________________ ____________
Yahoo! Messenger - Communicate instantly..."Ping"
your friends today! Download Messenger Now
http://uk.messenger.yahoo.com/download/index.html
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: malloc and free

At 06:39 PM 12/24/2004 +0000, Ankit Jain wrote:
>hi
>
>routine xyz uses malloc and free functions. it gives
>accurate and correct result if called once.
>
>but if the function is called in a loop N number of
>times then probably it gives segmentation fault.
>
>what is the reason? can any body guess or test code
>is needed?


Probably test code is needed. But if you want a guess ... the "free" call
contains an error that leads to a memory leak. If you call the routine
once, that's no big deal, and the routine will appear to return "accurate
and correct result". But if you call it a lot, memory consumption goes up
past the point where the kernel can support it and a segfault results.

That's just a shot in the dark, though ... and even it assumes that N is a
big number (thousands at least), not 10 or 20. Your use of "probably" does
make it an appealing guess, though.

Really, though, you are posing the question, "What can go wrong with
malloc() and free()?" Put that way, it is obvious that it is too vagure for
a troubleshooting list. Let's see the code, as well as whatever is calling
the code.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: malloc and free

--=-l070wRhFbmB+RbQQhMsW
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,
I have read that the malloc-ed memory is not actually freed upon
calling free, but is still maintained in the processes' malloc pool of
memory. So can that add to the memory leak attributing a segfault?
Please someone tell if I am wrong!!

On Sat, 2004-12-25 at 00:23, Ray Olszewski wrote:
> At 06:39 PM 12/24/2004 +0000, Ankit Jain wrote:
> >hi
> >
> >routine xyz uses malloc and free functions. it gives
> >accurate and correct result if called once.
> >
> >but if the function is called in a loop N number of
> >times then probably it gives segmentation fault.
> >
> >what is the reason? can any body guess or test code
> >is needed?
>=20
>=20
> Probably test code is needed. But if you want a guess ... the "free" call=
=20
> contains an error that leads to a memory leak. If you call the routine=20
> once, that's no big deal, and the routine will appear to return "accurate=
=20
> and correct result". But if you call it a lot, memory consumption goes up=
=20
> past the point where the kernel can support it and a segfault results.
>=20
> That's just a shot in the dark, though ... and even it assumes that N is =
a=20
> big number (thousands at least), not 10 or 20. Your use of "probably" doe=
s=20
> make it an appealing guess, though.
>=20
> Really, though, you are posing the question, "What can go wrong with=20
> malloc() and free()?" Put that way, it is obvious that it is too vagure f=
or=20
> a troubleshooting list. Let's see the code, as well as whatever is callin=
g=20
> the code.
>=20
>=20
>=20
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" i=
n
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs

--=20
With regards,

Jagadeesh Bhaskar P

--=-l070wRhFbmB+RbQQhMsW
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQBBzNumhmvCciYHkaMRAkjHAJwMrR3YWbNqBZA6bDRkcbkkl3yK1wCe L2a5
sOmhnmQIT7C4a3n/zGDqKno=
=5SBj
-----END PGP SIGNATURE-----

--=-l070wRhFbmB+RbQQhMsW--

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs