Help/Support Please Help Me GNU ( GDB ) Error IOS 9.2.1

[TestingHacks 1.2k 10 9.2]

Help Me GNU (GDB ERROR) 

(gdb) att binaryname 

result error   

[Joka 3.2k iPhone X 12.4]

Use LLDB instead.

[TestingHacks 1.2k 10 9.2]

Use LLDB instead.

LLDB ERROR 

 

process connect connect:xxxxx:xx

 

connection refuse

 

please help me

Use LLDB instead.

LLDB Windows 

LLDB Linux

LLDB Mac OSX

 

Result Error 

[Ratskillz 1 27]

Same with me for gdb, except for lldb I get another error about couldn't start thread or something

[Ratskillz 1 27]

LLDB ERROR 

 

process connect connect:xxxxx:xx

 

connection refuse

 

please help me

LLDB Windows 

LLDB Linux

LLDB Mac OSX

 

Result Error 

I fixed mine. A lot of stuff on this site is outdated. You need to extract debugserver from your xcode developer disk image for the iOS version you want. Then you need to sign it with codesign (access to all processes) so you wont get a "cant create thread" error, then you need to place that in usr/bin. You need to set the proper permissions(just chmod 755 debugserver in terminal) so you wont get a permission denied error. Then you can start debugserver and lldb from your mac terminal. I'm on iOS9.3.3, and this is also working up to 10.2 on any architecture. Goodluck.

 

Come to think of it, try setting the permissions for gdb(same command as above, just replace debugserver with gdb). Never tried it, but it might work.

Updated February 26, 2017 by Ratskillz

[TestingHacks 1.2k 10 9.2]

I fixed mine. A lot of stuff on this site is outdated. You need to extract debugserver from your xcode developer disk image for the iOS version you want. Then you need to sign it with codesign (access to all processes) so you wont get a "cant create thread" error, then you need to place that in usr/bin. You need to set the proper permissions(just chmod 755 debugserver in terminal) so you wont get a permission denied error. Then you can start debugserver and lldb from your mac terminal. I'm on iOS9.3.3, and this is also working up to 10.2 on any architecture. Goodluck.

 

Come to think of it, try setting the permissions for gdb(same command as above, just replace debugserver with gdb). Never tried it, but it might work.

thanks bro