You set me on the right path … I ran the app from the Finder and attached to it from Xcode …
The problem … running from Xcode the destination was 32 bit running from Finder we run in 64 bit a supporting library containing the call in question would not operate correctly in 64 bit thx … -koko On Oct 4, 2013, at 11:20 AM, Fritz Anderson <fri...@manoverboard.org> wrote: > On 4 Oct 2013, at 11:27 AM, koko <k...@highrolls.net> wrote: > >> I have a stack variable in an Obj-C Interface which is a C++ Class. I call >> a function of this class. If I run the app from XCode it works as expected, >> i.e. the function is called. >> >> But, if I run the app from the Finder the function is not called. >> >> What am I missing or should I say "How can this be?" > > From your description, there is absolutely no way of knowing. There could be > any number of conditions in the stack above the call site that only you know > about. > > Try running the application from the Finder, modified if necessary to loop > before getting to the call site, and attach command-line lldb (or even the > Xcode debugger) to it. > > The canonical reason a Mac application behaves differently in Xcode and in > real life is that you're depending on the working directory Xcode gives you. > Last I looked, it was the application directory under Xcode, and / from the > Finder. > > (Xcode. Lower-case c.) > > — F > > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
