On Sun, May 01, 2005 at 02:16:27PM -0400, Friends wrote:
Only when I compile with an optimization level of "O2" or "O3" does the program exit with a memory access error.
It may be a bug in GCC and it may also be a bug in your program (some problems like aliasing bugs only are exposed at higher levels of optimization).
Also uninitialized variable problems often show up only with optimization turned on (registers tend to be "more" uninitialized than memory :-)
