Simon, I'm getting constantly errors that I'm missing DLLs. It started with that allegro-debug-5.2.dll is missing. Can you say which of the countless instances you used (static or dynamic?, i686 or x86_64?, 5.2.3.0 or ~.1?). Do I need MingW?
After several hours of testing around I don't think I can build it without help. I actually don't even know when I successfully build such a build against debugging libraries.
New try:
Debugging DLLs/LIBs in reply #35's attachment. I didn't test anything earlier -- I made the archive, uploaded, and went to bed.
For both archives, I used allegro-i686-w64-mingw32-gcc-7.2.0-posix-dwarf-dynamic-5.2.3.1.zip.
I can probably rename the .libs as I want; at least when assuming the crazy workstyle that replaces release libs with debugging libs in the global compiler directory. But I shouldn't have renamed the DLLs. The DLLs should be called exactly as the your DLL-not-found error wants them.
If the DLLs are not found at runtime, even though you put correctly-named DLLs into the DMD dir, then put the DLLs in the game directory instead.
The callstack may show al_stricmp only because it happens to be the closest known address in the DLL to the numeric address value observed in the callstack. It may actually be some private audio function in Allegro that cannot be mapped to a name at runtime, since there is no information about that function name and address.
This is excellent insight. Thanks!
I didn't suspect this, I thought memory corruption was the only explanation. But in these January 2018 crash reports, the exact same message reproduces too well, it's probably not memory corruption.
At least I'm happy that I came to the same conclusion that A5 debugging builds might help.
No results for quick web search for crashes in al_create_voice. Tried some variation, but whenever the search becomes too detailed, it finds only this very thread, plus maybe raw Allegro source files. <_<;
-- Simon