# Cant see output of std::cout or DBG() anywhere? **URL:** \ **Category:** General JUCE discussion\ **Created:** [March 4, 2019, 1:06pm UTC](https://forum.juce.com/t/cant-see-output-of-std-cout-or-dbg-anywhere/32095 "2019-03-04T13:06:59Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![ComposerShield](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/composershield/32/6655_2.png) [@ComposerShield](https://forum.juce.com/u/ComposerShield)\ **Post date:** [March 4, 2019, 1:06pm UTC](https://forum.juce.com/t/cant-see-output-of-std-cout-or-dbg-anywhere/32095/1 "2019-03-04T13:06:59Z")
So I’ve never been able to debug using the tools everyone seems to be able to use in Youtube videos. Those functions don’t show up in the console at the bottom and even when I open the built application from the terminal, the messages don’t appear in the terminal. Anybody know what might be going on? ---
**Author:** ![daniel](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/daniel/32/790_2.png) [@daniel](https://forum.juce.com/u/daniel)\ **Post date:** [March 4, 2019, 1:09pm UTC](https://forum.juce.com/t/cant-see-output-of-std-cout-or-dbg-anywhere/32095/2 "2019-03-04T13:09:19Z")
Which IDE are you using? Are you building for debug? DBG is not executed in release builds… ---
**Author:** ![ComposerShield](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/composershield/32/6655_2.png) [@ComposerShield](https://forum.juce.com/u/ComposerShield)\ **Post date:** [March 4, 2019, 7:42pm UTC](https://forum.juce.com/t/cant-see-output-of-std-cout-or-dbg-anywhere/32095/3 "2019-03-04T19:42:42Z")
Xcode on a Mac. On the projucer it says debug is enabled. Here’s a screenshot, I assume I’m looking at the right thing. ![30%20PM](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/8/8fbeb0fc21151aa625ad59165f86f796c46cfd6e.png) ---
**Author:** ![asimilon](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/asimilon/32/4235_2.png) [@asimilon](https://forum.juce.com/u/asimilon)\ **Post date:** [March 4, 2019, 7:49pm UTC](https://forum.juce.com/t/cant-see-output-of-std-cout-or-dbg-anywhere/32095/4 "2019-03-04T19:49:38Z")
It’s a bit odd that you don’t see anything when running a built application. This took me far too long to realise how to do in the case of plugins : ![image](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/3/3b5294718af4b7576d282661fbf4488a33c5184c.png) Click the “Testing - Standalone Plugin” and switch to “VST3” (or AU). Click it again then choose “Edit scheme…” ![image](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/0/03b4934a126de57b78417c7019b40771fa987cc1.png) Click “Executable” and choose “Ask on launch”. Now when you build and run your plugin (CMD-R) you can choose your DAW to open, and you’ll see DBG output in the Debug Area Console (and be able to add breakpoints etc). ![image](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/0/0be87ff8486b735a9bf0a7ad96b9c1126e18ca35.png) ---
**Author:** ![ComposerShield](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/composershield/32/6655_2.png) [@ComposerShield](https://forum.juce.com/u/ComposerShield)\ **Post date:** [March 4, 2019, 10:01pm UTC](https://forum.juce.com/t/cant-see-output-of-std-cout-or-dbg-anywhere/32095/5 "2019-03-04T22:01:39Z")
Thanks! That worked when I opened it in Logic so that’s pretty neat and I’m happy. Just curious, is there a way to do this same process for standalone audio applications? When I did the same process for my standalone version, it kind of looked like it was working in that stuff was showing in the console but then my computer told me that the program wasn’t responding and I had to stop it. It was throwing up these errors in my process block where I was referencing the buffer so I think it might have something to do with that. ---
**Author:** ![asimilon](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/asimilon/32/4235_2.png) [@asimilon](https://forum.juce.com/u/asimilon)\ **Post date:** [March 5, 2019, 9:02am UTC](https://forum.juce.com/t/cant-see-output-of-std-cout-or-dbg-anywhere/32095/6 "2019-03-05T09:02:53Z")
You should find when you “Edit scheme…” of the Standalone Plugin that it defaults like this : ![image](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/1/1ef62054ab8a52c89de777b162ad8961d738ecaf.png) Without seeing some more details difficult to say what’s wrong, but there are many ways you could trip up with a standalone plugin (eg. trying to use the playhead information available from the host, which doesn’t work in a standalone)