Re: debugging Mac framework in Xcode 5.1.1
Re: debugging Mac framework in Xcode 5.1.1
- Subject: Re: debugging Mac framework in Xcode 5.1.1
- From: James Walker <email@hidden>
- Date: Wed, 23 Jul 2014 09:30:49 -0700
On 7/23/2014 8:28 AM, Fritz Anderson wrote:
On Jul 3, 2014, at 3:31 PM, James Walker <email@hidden> wrote:
I'm trying to debug a Mac framework (i386 architecture) with Xcode
5.1.1 under Mavericks. In the scheme editing panel, I've selected
the host app. Whether I use "launch automatically" or "wait for
launch", the app starts and then quits a second later. There's
nothing in Xcode telling me about a problem. In the system
console, I found messages saying that debugserver started and then
very soon stopped, and a message from launchd saying "Exited with
code: 45".
If I double-click the app and then use "attach to process", then
the debugger seems to immediately detach itself with no
explanation.
Any clues?
It’s twenty days since the original posting, but it only just came
through to me. If I can’t rely on delivery, I probably can’t rely on
seeing the answers, but…
First question: What’s the host? There is a system flag an
application can set to refuse execution if a debugger is attached.
Applications that enforce DRM, like iTunes, are the leading example.
Ah, I think you nailed it! It's my application too, but I was trying to
debug on a machine other than my usual development machine, and didn't
want to set things up to build everything there. I had forgotten that I
do have some anti-debugging code in the release build. Duh. I
eventually went ahead and set up enough to build the app on the test
machine, so the issue is moot now, but it's nice to have an explanation.
Thanks.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden