I have a C program that compiles and runs just fine on a G5 running Tiger 10.4.10. I'm using the -fast option with gcc when I compile. The program contains several malloc calls, but these are being handled correctly on the G5. When I compiled the same program on a MacBook Pro running Tiger 10.4.10, I get no compile-time errors or warnings, but at run-time the program crashes with a segmentation violation the first time it makes a malloc call. However, if I compile without the -fast flag, then the program runs fine on both the MacBook Pro and the G5 (although painfully slowly).
Has anyone seen this problem before? I'll be grateful for any suggestions about how to clear this up.
Has anyone seen this problem before? I'll be grateful for any suggestions about how to clear this up.