Forums > Dev

Debugging MSP external in XCode

March 12, 2007 | 2:19 pm

Hi,

I’ve been trying to debug an MSP external as described in the document:

http://www.cycling74.com/twiki/bin/view/ProductDocumentation/XcodeDebugging

I’ve configured XCode as described in this document, but whenever I try to start the debugger, I get the error message "No launchable executable present at path". I searched for this message via google, and apparently, a lot of people say that this is a bug in XCode and one just has to twiddle a bit to get around this. But I’ve tried copying the MaxMSPRuntime into the build directory, and that didn’t help. I tried copying my external into the path of the MaxMSPRuntime, and that didn’t help… In short I’ve twiddled, but it’s gotten me nowhere… Has anyone else seen this problem before?

And can anyone give me any general advice about debugging a MSP external? I don’t know how one is supposed to go about finding a problem in a MSP external without being able to print messages to the window.

Thanks,
Greg


March 12, 2007 | 3:04 pm

> And can anyone give me any general advice about debugging a MSP external? I don’t know how one is supposed to go about finding a problem in a MSP external without being able to print messages to the window.
>
>
Actually, I don’t know how you could debug an MSP external (if you mean
by debugging something realized inside the developing environment with a
lot of breakpoints, watches etc.), but I can print messages to the
window, even in my perform routines. Of course it wastes a lot of CPU,
but for testing purposes it works fine for me (I suppose you mean the
using of the "post" command).

Bye,
Adam


March 12, 2007 | 3:55 pm

On Mar 12, 2007, at 9:19 AM, Greg Kellum wrote:

> http://www.cycling74.com/twiki/bin/view/ProductDocumentation/
> XcodeDebugging
>
> I’ve configured XCode as described in this document, but whenever I
> try to start the debugger, I get the error message "No launchable
> executable present at path". I searched for this message via
> google, and apparently, a lot of people say that this is a bug in
> XCode and one just has to twiddle a bit to get around this. But
> I’ve tried copying the MaxMSPRuntime into the build directory, and
> that didn’t help. I tried copying my external into the path of the
> MaxMSPRuntime, and that didn’t help… In short I’ve twiddled, but
> it’s gotten me nowhere… Has anyone else seen this problem before?
>
> And can anyone give me any general advice about debugging a MSP
> external? I don’t know how one is supposed to go about finding a
> problem in a MSP external without being able to print messages to
> the window.

You should be able to print to the Max window. You could also print
to the console (view using Utilities/Console.app) by using something
like this:
float foo = 5.3;
fprintf(stderr, "some value: %f", foo);

Debugging using the runtime as specified in that link works fine for me.

good luck,
Tim


March 14, 2007 | 4:32 pm

Hi Tim,

Would you mind sending me an example project file in which the MaxMSPRuntime is called as well as a description of where the MaxMSPRuntime and the external has to be for this to work? I’ve spent another afternoon on this problem, and it’s still not working and I have no ideas left to try out.

Thanks,
Greg


Viewing 4 posts - 1 through 4 (of 4 total)