From: Sriharsha <sriharsha.v@redpinesignals.com>
To: gcc-help@gcc.gnu.org
Subject: Re: malloc and free
Date: Mon, 27 Dec 2004 17:45:00 -0000 [thread overview]
Message-ID: <41D04AF6.50504@redpinesignals.com> (raw)
In-Reply-To: <363801FFD7B74240A329CEC3F7FE4CC4030965C0@ntxboimbx07.micron.com>
What Irtaylor said is true:
Consider code such as this....
...
...
while(some_condition)
{
if(some_other_condition)
{
...
some_var = malloc(some_amount);
...
}
...
free(some_var);
}
...
...
Here, may be for the first time "some_other_condition" may be true, but
subsequently, it may be false due to which the free (or any code that
refers to some_var) fails.
lrtaylor@micron.com wrote:
>It's probably a bug in your routine. However, without seeing your code,
>it's hard to give any good answers. Step through it with a debugger and
>make sure that you're not trying to free the same memory more than once,
>or access memory that hasn't been allocated yet.
>
>Good luck,
>Lyle
>
>-----Original Message-----
>From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
>Behalf Of Ankit Jain
>Sent: Friday, December 24, 2004 11:41 AM
>To: gcc
>Subject: 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
>
>
>
>
>
>
--
*****************************
* Sriharsha Vedurmudi
* Software Engineer
*
* Redpine Signals Inc.
* Gate #395, Plot 87,88
* Sagar Society, Road #2,
* Banjara Hills,
* Hyderabad - 500 034
* www.redpinesignals.com
*
* +91-40-23559911 (Office)
* +91-98851-37338 (Mobile)
*****************************
next prev parent reply other threads:[~2004-12-27 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 17:38 lrtaylor
2004-12-27 17:45 ` Sriharsha [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-24 18:40 Ankit Jain
2004-12-29 9:54 ` Ken Foskey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41D04AF6.50504@redpinesignals.com \
--to=sriharsha.v@redpinesignals.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).