Re: XCode debug external process
Re: XCode debug external process
- Subject: Re: XCode debug external process
- From: Alex Zavatone <email@hidden>
- Date: Tue, 20 Dec 2016 16:10:27 -0600
Would the codesign tool be able to apply a dev profile to it so they the debugger can attach?
Sent from my iPhone
> On Dec 20, 2016, at 4:01 PM, Roland King <email@hidden> wrote:
>
> MacOS, totally unsigned, simple 3 file command line executable which compiles with make and runs right off the command line, no gui, no anything. I could convert it to an Xcode project but I didn’t think I’d have to. So I do believe it’s a tool signing/permission issue, as Sierra is very .. tight about such things .. but it seems it’s one Xcode doesn’t know to ask for permissions for.
>
> I’d dump more logs but I can’t find any
>
>
>> On 21 Dec 2016, at 05:57, Doug Hill <email@hidden> wrote:
>>
>> Are you trying to debug a macOS process, iOS, watchOS, etc.? The reason I ask is that signed Distribution apps on iOS can't be attached by a debugger. This is probably also true for macOS Distribution apps. I think you need e.g. a Development signed iOS app or unsigned Mac app to attach with debugger.
>>
>> Doug Hill
>>
>>
>>> On Dec 20, 2016, at 1:46 PM, Roland King <email@hidden> wrote:
>>>
>>> I have an executable not built with Xcode (but with make) I wanted to quickly debug a piece of. LLDB on the command line works but I’m not great with the commands for LLDB and GDB stopped working in Sierra unless you patch it, sign it and run it in a mode which leaves dead shells behind. So I wanted to use Xcode to debug it graphically.
>>>
>>> I remembered Xcode can debug external processs so I found the menu Debug->Attach To Process By PID Or Name …, added the executable name and Xcode duly waited. I launched from the command line and the code just ran to completion. Xcode did stop waiting but didn’t attach and the sole message in the debug log was
>>>
>>> Message from debugger: unable to attach
>>>
>>> I can debug if I use the ‘debug as root’ option, after authenticating, but that most certainly shouldn’t be necessary for a non-root process running as me in a shell running as me on a machine logged in as me.
>>>
>>> How can I fix this? Xcode is a useful graphical front-end to lldb and it’s handy to be able to use it. I suspect there’s some keychain or other authentication level now needed for lldb to be allowed to debug, but Xcode isn’t asking for it.
>
>
> _______________________________________________
> 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
_______________________________________________
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