0
0

Hello there!

I am working on an Adobe AIR project in which we link with FMOD via Adobe Native Extensions. It works well in some cases, but in one of our builds, we reliably get a SIGSEGV in fmod shortly after calling FMOD_EventSystem_Load() with some loaded FEV data.

Our Native Extension is in the form of a DLL which is dynamically linked with fmodex.dll and fmod_event.dll, using the MinGW compiler suite on Windows. The crash stack trace is as follows. Has anyone seen anything like this? I suspect that it is a problem with the way I am building or linking, but I am currently at an impasse.

Thanks!
JW

Thread [12] 0 (Suspended : Signal : SIGSEGV:Segmentation fault)
fmodex!FMOD_Geometry_AddPolygon() at 0x5a29571f
fmodex!?createSoundInternal@SystemI@FMOD@@QAG?AW4FMOD_RESULT@@PBDIIIPAUFMOD_CREATESOUNDEXINFO@@PAPAVFile@2@_NPAPAVSoundI@2@@Z() at 0x5a2e8d90
fmodex!?createSoundInternal@SystemI@FMOD@@QAG?AW4FMOD_RESULT@@PBDIIIPAUFMOD_CREATESOUNDEXINFO@@PAPAVFile@2@_NPAPAVSoundI@2@@Z() at 0x5a2e8e1a
KERNEL32!BaseCleanupAppcompatCacheSupport() at 0x7592339a
0x4a18460
0x5d3f9e8
ntdll!RtlpNtSetValueKey() at 0x772d9ef2
0x4a18460
0x72a77a8d
0x0

  • You must to post comments
0
0

Turns out this was a bit of a red herring. FMOD was SIGSEGV, but it was because of of a crash/termination of the main thread of the Adobe AIR app, which was freaking out one of the FMOD threads. Worked around the Adobe issue and everything is now hunky-dory.

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.