# Debugging AU in Logic changes? **URL:** \ **Category:** MacOSX and iOS\ **Created:** [June 14, 2023, 8:57am UTC](https://forum.juce.com/t/debugging-au-in-logic-changes/56645 "2023-06-14T08:57:03Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![leehu](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/leehu/32/3280_2.png) [@leehu](https://forum.juce.com/u/leehu)\ **Post date:** [June 14, 2023, 8:57am UTC](https://forum.juce.com/t/debugging-au-in-logic-changes/56645/1 "2023-06-14T08:57:03Z")
Hi, since updating to latest Logic (10.7.8) my normal method for debuggins AU in Logic no longer works. I normally: 1. Switch to Rosetta mode so that AU is loaded inline rather than out of process 2. Launch Logic through debug in XCode This has always work fine in the past but gone to debug something today and it’s not being picked up the debugger. ANyone else come across similar? Thx ---
**Author:** ![HowardAntares](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/howardantares/32/4629_2.png) [@HowardAntares](https://forum.juce.com/u/HowardAntares)\ **Post date:** [June 14, 2023, 2:23pm UTC](https://forum.juce.com/t/debugging-au-in-logic-changes/56645/2 "2023-06-14T14:23:57Z")
I had to turn off SIP for that to work. I don’t have a link handy for the instructions on how to do that, sorry. It still took almost a minute the very first time I tried before it allowed debugging. ---
**Author:** ![leehu](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/leehu/32/3280_2.png) [@leehu](https://forum.juce.com/u/leehu)\ **Post date:** [June 14, 2023, 5:51pm UTC](https://forum.juce.com/t/debugging-au-in-logic-changes/56645/3 "2023-06-14T17:51:45Z")
hmmmm… maybe this is it. maybe I disabled that on the other mac and not on this one. seems extreme to have to do this tho. ugh, will give it a go next week., though i’m pretty sure I’ve debugged AUs on this mac. thx ---
**Author:** ![chkn](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/chkn/32/3862_2.png) [@chkn](https://forum.juce.com/u/chkn)\ **Post date:** [September 22, 2023, 10:46am UTC](https://forum.juce.com/t/debugging-au-in-logic-changes/56645/4 "2023-09-22T10:46:11Z")
Did you use the Rosetta Destination in Xcode? You have to make it visible in Xcode 14/15 first, they are hidden by default (I just stumbled over this, too) Product \> Destination \> Destination Architectures \> Show Rosetta Destinations \> Show Both BTW Is disabling SIP still the only possibility to debugging arm-builds in Logic? Will there ever be a possibility without disabling SIP? @mfritze ---
**Author:** ![anthony-nicholls](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/anthony-nicholls/32/1246_2.png) [@anthony-nicholls](https://forum.juce.com/u/anthony-nicholls)\ **Post date:** [September 22, 2023, 10:53am UTC](https://forum.juce.com/t/debugging-au-in-logic-changes/56645/5 "2023-09-22T10:53:45Z")
> [@chkn](#): > > Is disabling SIP still the only possibility to debugging arm-builds in Logic? To the best of my knowledge, yes. This is supported by official Apple documentation. > Attaching to system processes requires disabling system integrity protection in macOS before debugging. > **[Debugging Out-of-Process Audio Units on Apple Silicon | Apple Developer...](https://developer.apple.com/documentation/audiounit/debugging_out-of-process_audio_units_on_apple_silicon)** > > Connect to out-of-process audio units using the Xcode debugger. ---
**Author:** ![mfritze](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/mfritze/32/9008_2.png) [@mfritze](https://forum.juce.com/u/mfritze)\ **Post date:** [September 28, 2023, 4:36pm UTC](https://forum.juce.com/t/debugging-au-in-logic-changes/56645/6 "2023-09-28T16:36:00Z")
Please file bug reports against macOS (please not against Logic or GarageBand, there is nothing we can do about it) in regards of Audio Unit debugging. The more the better. ---
**Author:** ![peteatjuce](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/peteatjuce/32/2347_2.png) [@peteatjuce](https://forum.juce.com/u/peteatjuce)\ **Post date:** [March 6, 2025, 11:50am UTC](https://forum.juce.com/t/debugging-au-in-logic-changes/56645/7 "2025-03-06T11:50:04Z")
I thought I’d add some info in case it helps. It can be easier to debug AUv3 on Intel, you have a spare Intel Mac. There is no need to deal with SIP for starters! How to debug your AUv3 on _Intel_ Mac (verified just now with macOS 15.3.1) Switch to your AUv3 target/project, set one or more breakpoints in your AUv3 Project schema: - set Executable to Logic Pro (for example) - set Wait for the Executable to be launched To debug: - Run Logic Pro (or whatever you’re testing under) - review that your breakpoints are still active (some might be de-activated) - Open a Logic project that uses your AUv3 All nice and easy! Best wishes, Pete ---
**Author:** ![peteatjuce](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/peteatjuce/32/2347_2.png) [@peteatjuce](https://forum.juce.com/u/peteatjuce)\ **Post date:** [March 6, 2025, 12:14pm UTC](https://forum.juce.com/t/debugging-au-in-logic-changes/56645/8 "2025-03-06T12:14:36Z")
I also wanted to note that when debugging an AUv3, the call to: ```auto File::getSpecialLocation(...hostApplicationPath...) ``` won’t return the path of the host application; rather, it returns the path of the AUv3. This means that code to check the plug-in host will never work as expected, e.g.: ```auto juce::PluginHostType plugin_host; if (plugin_host.isLogic() == true) { // This will never be hit for AUv3! } ```