Opened 14 years ago
Last modified 13 years ago
#781 closed defect
csc -c++ produces executables that hang under Mac OS X — at Version 3
| Reported by: | Ivan Raikov | Owned by: | felix winkelmann |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | build system | Version: | 4.7.x |
| Keywords: | Cc: | ||
| Estimated difficulty: |
Description (last modified by )
It appears that compiling programs 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
Change History (3)
comment:1 follow-up: 2 Changed 14 years ago by
| Owner: | set to felix winkelmann |
|---|---|
| Status: | new → assigned |
comment:2 Changed 14 years ago by
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
cscinvocations.
comment:3 Changed 14 years ago by
| Description: | modified (diff) |
|---|---|
| Summary: | Unit tests for bind hangs under Mac OS X → csc -c++ produces executables that hang under Mac OS X |

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
cscinvocations.