Compiler build error

Nicholas Wilson iamthewilsonator at hotmail.com
Sun Aug 5 01:15:07 UTC 2018


On Saturday, 4 August 2018 at 18:12:05 UTC, Alex wrote:
> On Saturday, 4 August 2018 at 13:26:01 UTC, Nicholas Wilson 
> wrote:
>>> 0  ldc2                     0x0000000106fcc4e7 
>>> llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 37
>>> 1  ldc2                     0x0000000106fcb9ea 
>>> llvm::sys::RunSignalHandlers() + 83
>>> 2  ldc2                     0x0000000106fcc90e 
>>> SignalHandler(int) + 239
>>> 3  libsystem_platform.dylib 0x00007fff5992af5a _sigtramp + 26
>>> 4  libsystem_platform.dylib 0x000000015fcde600 _sigtramp + 
>>> 104543936
>>> ldc2 failed with exit code -11.
>>>
>> Is this the entire stack trace? If dmd is also affected 
>> chances it is a frontend bug.
>
> Well, on MacOs - yes. On a Linux, it is longer:
>
> [snip]

That is a very long stacks trace and combined with the very short 
stack trace on OSX, this is probably a stack overflow.
1) Do you have any very deeply nested types/templates somewhere 
or somehow created a cyclic dependency in semantic analysis?
2) Can you try with a bigger stack (ulimit -s)? If it still fails 
then its probably 1.


More information about the Digitalmars-d-learn mailing list