C programming doubt ?

Replies

• 

  gaurav.bhorkar

  I think it will crash the program because you have created an invalid reference to the block of 100 bytes of allocated memory.
  
  I'm not sure though. Did the program run?
• 

  csiscool

  Nice Question..
  
  this code results in memory leak.
• 

  Sachin Jain

  @ csiscool
  Can you please explain more ?
• 

  nansijs

  I think the program cause memory leak. That is the allocated memory cannot be used by another application.
• 

  pradeep_agrawal

  Based on ANSI C specification, if the argument passed to free does not matches with value returned by malloc/calloc/realloc, or if the space has already been freed by calling free or realloc then the behavior is undefined.
  
  With this i feel the behavior can be different based on the compiler being used. If the code is compiled using gcc then the program will crash at free itself.
  
  -Pradeep
  
• 

  vik001ind

  int *ptr; // this is a pointer of int type
  ptr = malloc(100);
  /* ERROR - malloc returns pointer of void type (void *), it is incompatible typecasting.
  Correct statement - ptr = (int *)malloc(100); Here we are dynamically allocating an array of 50 integers (considering 16 bit compiler). */
  ptr++; // PTR IS NOW POINTING TO NEXT INT
  free(ptr); // ERROR - deallocating the pointer which contains the wrong address. Allocation of memory is done to different address.
  
  Program may result in segmentation fault. Memory leak is a different concept altogether.
• 

  PraveenKumar Purushothaman

  I got System Error and as said here, it caused a memory issue... Since I worked on a virtual machine, it crashed the system too. I used 64 MB of RAM and when I restarted it, it was fine. 😐 It causes a Segmentation Fault! 😀