Re: gcc 3.3.6 - stack corruption questions

[Louis LeBlanc <leblanc@keyslapper.net>]

On 07/25/05 05:15 PM, Giovanni Bajo sat at the `puter and typed:
> 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
> -- 

Thanks for the tips.  Since I'm on Solaris, I don't think Valgrind is
an option (Linux and FreeBSD on x86/PowerPC/AMD64 only).

I will check out the gcc versions and features you mention.

Lou
-- 
Louis LeBlanc                                 leblanc@keyslapper.net
Fully Funded Hobbyist,                   KeySlapper Extrordinaire :þ
http://www.keyslapper.net                                       Ô¿Ô¬
Key fingerprint = C5E7 4762 F071 CE3B ED51  4FB8 AF85 A2FE 80C8 D9A2

Turnaucka's Law:
  The attention span of a computer is only as long as its electrical cord.