[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gnugo-devel] Crash report for OS X Segmentation fault

From: Marco Scheurer
Subject: Re: [gnugo-devel] Crash report for OS X Segmentation fault
Date: Wed, 9 Jan 2002 12:19:51 +0100

On Tuesday, January 8, 2002, at 07:25  pm, Gunnar Farneback wrote:

Teun wrote:
I think then this is a problem with stack overflow.
We have seen something similar earlier on with
the owl stack, which was much larger though.

Or heap overflow. I think it's odd that the compiler or linker can't
warn about this.

Yes, in 10 years of development on NeXTSTEP, OPENSTEP, now Mac OS X, I've never seen this. I don't know enough about compilers or gcc to decide if this a bug though.

If anyone cares, cc -v gives:
Apple Computer, Inc. version gcc-934.3, based on gcc version 2.95.2 19991024 (release)

I bet declaring this array as static or allocating
it with malloc should also fix
this problem.

I also think that's very likely. Allocating it as static would be
easiest and probably good enough.

Yes, declaring it static fixes the problem. I'm not familiar with contributing code or patches to gnugo, so could please one of you guys fix it? Thanks.


Marco Scheurer
Sen:te, Lausanne, Switzerland

reply via email to

[Prev in Thread] Current Thread [Next in Thread]