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: A simple program with a large array segfaults

From: Mike Stump <mrs at apple dot com>
To: Gowri Kumar CH <gkumar007 at gmail dot com>
Cc: Andrew Pinski <pinskia at physics dot uc dot edu>, gcc at gcc dot gnu dot org
Date: Thu, 4 Jan 2007 11:46:46 -0800
Subject: Re: A simple program with a large array segfaults
References: <526520db0701040411y7c7af69es51c99aaa091e063d@mail.gmail.com> <200701041218.l04CIpc9027245@localhost.localdomain> <526520db0701040849n6845e5bdqe6c9313cb010a091@mail.gmail.com>

On Jan 4, 2007, at 8:49 AM, Gowri Kumar CH wrote:

Is this one of the things which we come to know by experience?

Yes.

Is there a way to find it out from the core/code generated?

No. You'd have to have someone tell you, or read up on a UNIX internals book or find a good C book.

I'm wondering how difficult it would be find this sort of errors in a large program.

You would be able to find this type of problem fairly easily in a large program, now. :-)

References:
- A simple program with a large array segfaults
  - From: Gowri Kumar CH
- Re: A simple program with a large array segfaults
  - From: Andrew Pinski
- Re: A simple program with a large array segfaults
  - From: Gowri Kumar CH

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