Bug 22592 – importC: Segmentation fault indexing global array at run-time

Compile with -betterC and run the resultant executable. --- /* Comment out the next line to make the segfault go away. */ int testfn (void); typedef struct config_s { short field; } config; static const config table[10] = { {0}, {4}, {5}, {6}, {4}, {16}, {16}, {32}, {128}, {258} }; int testfn () { return table[6].field; } int main() { testfn(); } ---

Seems to be another regression caused by https://github.com/dlang/dmd/pull/13399

As far as I understand it, the issue is that SCstatic is not set until the variable is known to be going to object file. However it is referenced *before* this, so all code generated until SCstatic gets set assumes that the global will be SCglobal. This is why the segfault occurs. Setting SCstatic at Symbol generation time of course fixes this, but I'm not in a position to say that is the correct thing to do here.

I clearly took the wrong approach in solving that problem.

(In reply to Iain Buclaw from comment #0) > Compile with -betterC and run the resultant executable. I think you meant compile as a C file.

@WalterBright created dlang/dmd pull request #13422 "fix Issue 22592 - importC: Segmentation fault indexing global array a…" fixing this issue: - fix Issue 22592 - importC: Segmentation fault indexing global array at run-time https://github.com/dlang/dmd/pull/13422

dlang/dmd pull request #13422 "fix Issue 22592 - importC: Segmentation fault indexing global array a…" was merged into stable: - a9247881dcbcbfbd871d75ebb95bd13ef5527752 by Walter Bright: fix Issue 22592 - importC: Segmentation fault indexing global array at run-time https://github.com/dlang/dmd/pull/13422

*** Issue 22590 has been marked as a duplicate of this issue. ***