Re: double free
From: Alan Balmer (albalmer_at_att.net)
Date: 07/01/04
- Next message: Case -: "Re: [OT] Re: memcpy() vs. for() performance"
- Previous message: Case -: "Re: double free"
- In reply to: weaselboy1976: "double free"
- Next in thread: jacob navia: "Re: double free"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 01 Jul 2004 11:52:07 -0700
On 1 Jul 2004 11:27:36 -0700, weaselboy1976@yahoo.com (weaselboy1976)
wrote:
>Hello
>
>Does anyone know of a good website that actually describes and
>demonstrates WHY freeing a pointer more than once is a problem. I'm
>specifically interested in what the ill effects are.
You probably won't find such a site, because the effects are
implementation dependent. On at least some implementations, it can
corrupt the heap.
>
>Also, if you know of any really good books that describe everything
>about memory in a c program ...
>
Same problem - dependent on architecture and runtime implementation.
>Thanks in advance!
Obviously the proper way to handle freeing a pointer more than once is
"Don't do it!" If you have a reason to know the effects on a
particular implementation, you need to find a newsgroup or other
source of information which deals with that particular implementation,
because it will be off-topic here.
-- Al Balmer Balmer Consulting removebalmerconsultingthis@att.net
- Next message: Case -: "Re: [OT] Re: memcpy() vs. for() performance"
- Previous message: Case -: "Re: double free"
- In reply to: weaselboy1976: "double free"
- Next in thread: jacob navia: "Re: double free"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
