ldc2 failed with exit code -1073741819.

kinke noone at nowhere.com
Wed Jan 19 01:17:40 UTC 2022


On Tuesday, 18 January 2022 at 16:25:45 UTC, Anonymouse wrote:
> What can I *reasonably* do here? Do I *have* to compile LDC 
> from source, to get debug symbols? How else can I reduce it 
> when it doesn't say what goes wrong?

[-1073741819 == 0xc0000005 => access violation]

Some options:

1. This might be 'caught' by an existing assertion. You can use a 
CI build (https://github.com/ldc-developers/ldc/releases/tag/CI) 
with enabled assertions to check.
2. In case the segfault does NOT happen in the frontend, enabling 
verbose codegen via `-vv` can be of great help to see what the 
glue layer was doing right before the crash (at the end of the 
potentially huge log). My manual reductions usually start there 
for glue layer crashes.



More information about the Digitalmars-d-learn mailing list