Happy to hear you've got Lix built and running on Mac first try!
The magic pink bug will glaringly surface in level 17, Beneath the Lab, if you continue to play the levels that Lix selects by default (lemforum/Lovely). It's possible that the bug won't hit you.
I agree that we shouldn't invest more time into Windows versions of Lix in Wine on Mac then. Thanks for posting the backtrace still!
I'm posting this for my own possible future investigation.
Unhandled exception: page fault on read access to 0x000000e300000013 in 64-bit code (0x000001401bb350).
Backtrace:
=>0 0x000001401bb350 in lix (+0x1bb350) (0x0000000011f590)
1 0x000001401a00eb in lix (+0x1a00eb) (0x0000000011f720)
2 0x000001401a8753 in lix (+0x1a8753) (0x0000000011f720)
[...]
13 0x000001401c95ca in lix (+0x1c95ca) (0000000000000000)
14 0x0000007b627fe9 in kernel32 (+0x27fe9) (0000000000000000)
15 0x0000017005d668 in ntdll (+0x5d668) (0000000000000000)
It loads and runs Lix, then crashes from within Lix with page fault.
Page fault from Wine can be anything: Bug in Wine, strangeness in the Windows D compilers, a latent crashing bug in Lix that has never surfaced in native builds, ...
I can build a 64-bit debugging Windows version, i.e., identical to the Windows 64-bit build that oxes has run, but in debug mode instead of release mode. When we run that in Wine on Mac, we'll see the function names in the stack trace instead of the opaque function addresses.
-- Simon