Exported VST causing Access Violations
-
@Adam_G But I'm not the only one who makes videos about debugging with xcode :)
-
@d-healey i found one other one! xD ( big thanks to @Dan-Korneff )
now my mac virtual machine is apparently too slow to build the debug version in xcode without getting out of memory errors smh.
can i get the same info from doing this process on windows? that question is mostly for @Christoph-Hart
-
@Adam_G I think you can avoid the memory issue if you reduce the number of compile threads (don't ask me how)
-
This post is deleted! -
defaults write com.apple.Xcode PBXNumberOfParallelBuildSubtasks 8
in terminal to reduce compile threads
-
@d-healey still seems to be hanging on 299 of 302 steps :(
-
can i get the same info from doing this process on windows?
Sure, if it also crashes on Windows, you can debug it there, no need to run a VM.
-
@Christoph-Hart thanks Christoph :)
-
@Adam_G said in Exported VST causing Access Violations:
@d-healey still seems to be hanging on 299 of 302 steps :(
How long did you wait?
-
@d-healey its still running right now
-
@Adam_G Yeah that's not right
-
@d-healey i shut it down, but now im struggling to complete the process in visual studio as the instructions are for xcode. i can compile the .vcxproj but i cant see where to set the daw to open it with
-
@Adam_G VS Menu -> Project -> Properties (last item) -> Debugging -> Command -> Browse.
-
@Christoph-Hart thank you! on windows vsts dont compile directly to the vst folder. do i need to set that for my working directory ? im using Reaper and the vst isnt showing up when i start debugging
-
anybody out there familiar with debugging in visual studio?
-
This should get you started (it's what I used)
-
@d-healey thank you very much
-
i think i managed to make it work thanks to everyones help. no crash in reaper but i replicated it in FL studio. is this what im after?
Exception thrown at 0x00007FFD4CA49F35 (myVST.vst3) in FL64.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.
-
@Adam_G No it seems that you're still using the release build in FL Studio - it should break in MSVS with the exact line that causes the crash. Make sure you load the correct plugin version (it should have a Debug postfix).
-
@Christoph-Hart hmm i compiled the vst with the debug version of hise standalone. i must be missing a step, ill try again