regarding free

From: sam_cit@xxxxxxxxxxx
Date: 14 Jan 2007 00:16:55 -0800

Hi Everyone,

int main()
{
char *p = malloc(100);
p = "india"; //assuming p is not null
p++;
free(p);
}

How would free() behave when the address passed is different from the
one that was allocated... would it fail? would it be a memory leak?

.

Follow-Ups:
- Re: regarding free
  - From: Mark McIntyre
- Re: regarding free
  - From: junky_fellow@xxxxxxxxxxx
- Re: regarding free
  - From: David T. Ashley
- Re: regarding free
  - From: Richard Heathfield
- Re: regarding free
  - From: Ian Collins

Prev by Date: Re: pre-processor string replacement
Next by Date: Re: pre-processor string replacement
Previous by thread: pre-processor string replacement
Next by thread: Re: regarding free
Index(es):
- Date
- Thread

Relevant Pages

memory leak detection using vc++ does not report line info
... I'm using VC++ to find memory leak information however, ... normal block at 0x003225C0, 10 bytes long. ... int main(int argc, char **argv) { ...
(microsoft.public.vc.debugger)
Re: bare bones file encrypter/decrypter using 128 bit Serpent algorithm
... int crypto(FILE *infile, char *action, char *name) ... crypto is a bad name, I suggest you ...
(comp.lang.c)
SSPI Kerberos for delegation
... const char *tokenSource, const char *name = NULL, ... DWORD bufsiz = sizeof buf; ... int n = ib.cbBuffer; ... // wserr() displays winsock errors and aborts. ...
(microsoft.public.dotnet.framework.remoting)
[EXPL] ELOG Remote Shell Exploit
... char content; ... static int content_length; ... static unsigned char boundary; ... void get_server_version; ...
(Securiteam)
[PATCH 1/4] v9fs: rename non-vfs related structs and functions to be moved to net/9p
... char *str; ... u32 version; ... struct v9fs_qid *qid) ... *wstat, int extended) ...
(Linux-Kernel)