csc -c++ produces executables that hang under Mac OS X

[Ivan Raikov]

It appears that compiling programs under Mac OS X with csc -c++ produces executables that hang when run. dtruss shows the following output, over and over:

sigprocmask(0x1, 0x0, 0x7FFF6A635BB0) = 0x0 0
sigaltstack(0x0, 0x7FFF6A635BA0, 0x0) = 0 0
sigprocmask(0x3, 0x7FFF6A635BB0, 0x0) = 0x0 0
sigreturn(0x0, 0x80000000, 0x0) = 0 0

[felix winkelmann]

Ivan, can you tell me where exactly it hangs? Does the compilation fail, or the execution of the compiled test programs? In the former case you can modify the test-script and add "-verbose -debug p" to the csc invocations.

[Ivan Raikov]

It seems that any program compiled with csc -c++ hangs when it is run, so I am changing the description of this issue. To be clear, compilation succeeds (produces an executable) but the executable hands when it is run.

Replying to felix:

Ivan, can you tell me where exactly it hangs? Does the compilation fail, or the execution of the compiled test programs? In the former case you can modify the test-script and add "-verbose -debug p" to the csc invocations.

[Jim Ursetto]

Maybe it's using clang or llvm-gcc. Symptom: running executable with -:d shows a stack at 0x0. If so, try latest stability or master.

[Ivan Raikov]

Running the executable with -:d gives the following output:

[debug] application startup...
[debug] heap resized to 500000 bytes
[debug] stack bottom is 0x7fff68e23be0.
[debug] entering toplevel toplevel...
[debug] entering toplevel toplevel...
[the last line repeats forever]

But it is true that while this instance of Chicken is built with C_COMPILER=gcc-4.2, I am not setting the variable CXX_COMPILER. I will try the latest master with llvm-gcc, thanks for your work on this.

[felix winkelmann]

This seems to me more an issue with the Mac OS build tools. I postpone this, unless someone objects.