This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Abnormal behavior of malloc in gcc-3.2.2

From: Nicholas Nethercote <njn at cs dot utexas dot edu>
To: Giovanni Bajo <giovannibajo at libero dot it>
Cc: Sandeep Kumar <sandeepksinha at gmail dot com>, gcc at gcc dot gnu dot org
Date: Mon, 21 Nov 2005 11:58:00 -0600 (CST)
Subject: Re: Abnormal behavior of malloc in gcc-3.2.2
References: <37d33d830511202058x427b207em83fcf635199d9acb@mail.gmail.com> <200511210502.jAL52OhK031716@earth.phy.uc.edu> <37d33d830511202114m10229cfeu94b5cd7335eb5bab@mail.gmail.com> <038d01c5ee8d$71e4d9f0$95b12997@bagio>

On Mon, 21 Nov 2005, Giovanni Bajo wrote:

I didnt get your point. I am allocating space only for 400 inregers
then as soon as in the loop if it crosses the value of 400 , it should
have given a segementation voilation ?


No. For that to happen, you need some memory checker. GCC has -fmudflap, try
with that. Recent versions of glibc also have their internal memory buffer
checker, it probably triggers the segmentation fault when you free the buffer
which you have overflown.

Valgrind will find this error too (www.valgrind.org).

Nick

References:
- Abnormal behavior of malloc in gcc-3.2.2
  - From: Sandeep Kumar
- Re: Abnormal behavior of malloc in gcc-3.2.2
  - From: Andrew Pinski
- Re: Abnormal behavior of malloc in gcc-3.2.2
  - From: Sandeep Kumar
- Re: Abnormal behavior of malloc in gcc-3.2.2
  - From: Giovanni Bajo

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]