This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.3.6 - stack corruption questions
- From: "Giovanni Bajo" <rasky at develer dot com>
- To: "Louis LeBlanc" <leblanc at keyslapper dot net>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Mon, 25 Jul 2005 17:15:41 +0200
- Subject: Re: gcc 3.3.6 - stack corruption questions
- References: <20050725145524.GB71939@keyslapper.net>
Louis LeBlanc <leblanc@keyslapper.net> wrote:
> The problem is I'm getting core dumps (SEGV) that appears to come from
> this code when I know it shouldn't be in the execution path. The code
> in question is switched on by a command line argument only, and the
> process is managed by a parent process that monitors and manages it's
> execution - reporting crashes and restarting it if necessary.
Looks like a bug hidden in your code. Several things you could try:
- valgrind
- GCC 4.0 with -fmudflap
- GCC 4.1 CVS with -fstack-protect
--
Giovanni Bajo