Curious segmentation fault...

1 msg	Re: C++ auto_ptr template query solved
2 msg	ISO C++
3 msg	LD_LIBRARY_PATH needed for gcc-3.4.5 executable
2 msg	mark.urs
3 msg	problem with catalog()
2 msg	AMD64 ABI and comparison of structures
1 msg	use of changes in STL library
6 msg	functions calls Vs calls using function pointers
1 msg	have the experience but no degree, we can help
1 msg	Generate listing files
1 msg	Relinking GCC as Static?
1 msg	How can compiled file include preprocessor macr...
1 msg	what should we do next step.
2 msg	C++ auto_ptr template query
3 msg	ARM Inline Assembler and 64 bit variables
7 msg	Linking un-referenced function

Curious segmentation fault...
\ Shriramana Sharma (22 May 2006)
. \ Shriramana Sharma (22 May 2006)
. \ Andrew Haley (23 May 2006)
. . \ Shriramana Sharma (24 May 2006)
. . . \ Andrew Haley (24 May 2006)
. . . . \ Shriramana Sharma (25 May 2006)

3 msg	problem passing constants to inline asm
1 msg	[Platform specific] About data segment
3 msg	OpenSource alternative to Purify memory debugger??

Subject:	Curious segmentation fault...
Group:	Gcc-help
From:	Shriramana Sharma
Date:	22 May 2006

Dear list,

Namaste (hello). This is my first post. I wonder if I have found a bug or at
least an anomalous behaviour in GCC. Please download the file segfault.tar.gz
from:

http://www.yousendit.com/transfer.php?action=download&ufid=0D3E9B791AE99BEA

(available for seven days from now). Do make and test both monthpan and
monthpan-bug with any date range that contains a Sunday (which is where the
bug lies). You should find that monthpan creates an output file called
monthpan.txt whereas monthpan-bug creates a segmentation fault at
grahanaama[0] (grahanaama means "weekday name").

The only difference between the two source files monthpan.c and monthpan-bug.c
is that the latter contains the line:

char spicanaama[] = "Spica";

*before* the start of the declarations of the two-dimensional arrays, which
for some reason seems to cause the zero element of the first two-dimensional
array to be out-of-bounds.

This problem confirmed on gcc-4.1/glibc-2.4 and gcc-3.35/glibc-2.34.

Please can anyone enlighten me as to what exactly causes this bug? Is it a bug
with GCC? If yes, where do I report it?

Thanks.

--

Tux #395953 resides at http://samvit.org
playing with KDE 3.51 on SUSE Linux 10.1
$ date [] CCE +2006-05-22 W21-1 UTC+0530