Hi,
Quick question, as root shouldn't I have. UID 0? I'm worried that something's wrong, I appear to have full access to files etc but not true root. My UID in the root shell is 10143 and even if that gives access to most stuff Im still not rooted.
Any ideas?
Cheers
Sent from my SO-01B using XDA App
ddewbofh said:
Hi,
Quick question, as root shouldn't I have. UID 0? I'm worried that something's wrong, I appear to have full access to files etc but not true root. My UID in the root shell is 10143 and even if that gives access to most stuff Im still not rooted.
Any ideas?
Cheers
Sent from my SO-01B using XDA App
Click to expand...
Click to collapse
Scratching my head currently to figure out the same
well it seems that this method of root messes with the sh binary installed under /system/bin/ so that it launches as user root. It doesn't seem to be the case like a normal linux box you would expect.
Also wondering whats the purpose of the su binary installed at step 4. Most probably to be able to run any command with super user privileges... but doesn't seem to work that way.
For example when I execute su /system/bin/sh, I get:
/system/bin/sh: 1: Syntax error: word unexpected (expecting ")")
Still trying to figure out whats going on...
j4mm3r said:
Scratching my head currently to figure out the same
well it seems that this method of root messes with the sh binary installed under /system/bin/ so that it launches as user root. It doesn't seem to be the case like a normal linux box you would expect.
Also wondering whats the purpose of the su binary installed at step 4. Most probably to be able to run any command with super user privileges... but doesn't seem to work that way.
For example when I execute su /system/bin/sh, I get:
/system/bin/sh: 1: Syntax error: word unexpected (expecting ")")
Still trying to figure out whats going on...
Click to expand...
Click to collapse
In my case not having UID 0 wrecks havoc with some apps.
I'll try reflashing one more time but so far it looks more like the system's been modified to appear rooted rather than actually being rooted.
ddewbofh said:
In my case not having UID 0 wrecks havoc with some apps.
I'll try reflashing one more time but so far it looks more like the system's been modified to appear rooted rather than actually being rooted.
Click to expand...
Click to collapse
oh no its rooted allright... otherwise there is no way that you could write to the /system file system.
Its just that its rather unconventional. Further more I'm beginning to get concerned about controlling the root access. I mean there are references to Superuser Whitelist applications which can alert when an app tries to request root access.
Till now my attempt to download an install "Superuser Whitelist" from the market has failed because that wants to install itself with the same user id as Android System, but its apk isnt signed with the same signature, so the system rejects the installation.
Trying to find alternatives... any help guys?
j4mm3r said:
oh no its rooted allright... otherwise there is no way that you could write to the /system file system.
Its just that its rather unconventional. Further more I'm beginning to get concerned about controlling the root access. I mean there are references to Superuser Whitelist applications which can alert when an app tries to request root access.
Till now my attempt to download an install "Superuser Whitelist" from the market has failed because that wants to install itself with the same user id as Android System, but its apk isnt signed with the same signature, so the system rejects the installation.
Trying to find alternatives... any help guys?
Click to expand...
Click to collapse
It's not rooted, it's been compromised. Only if you have a proper root (aka UID 0) you can call it rooted.
And the fun continues, if I start up the adb shell I'm still logged on as the shell user with an uid of 2000. Egad!
Yeah, it's definite. We're not rooted. We have better access to system files but it's not a root, not by a long shot.
Same here. Could it be an issue with busybox?
same with mine.. so does this mean that some of us don't have it rooted? or that the original devs were wrong when they said they rooted it?
if it's the first, i'll just try again..
instigator008 said:
Same here. Could it be an issue with busybox?
Click to expand...
Click to collapse
I have no idea, but it's annoying to not have access to the init scripts. :/
ddewbofh said:
I have no idea, but it's annoying to not have access to the init scripts. :/
Click to expand...
Click to collapse
errr... why not the init scripts? you can modify any file that you want. I'm still checking the issue with the id.
I ran strace on a binary and basically its the egid which is 0 so.
Code:
# strace id
strace id
execve("/system/bin/id", ["id"], [/* 8 vars */]) = 0
syscall_983045(0x700189fc, 0, 0x7ee18da4, 0x1, 0x700189fc, 0x7ee18da0, 0x70010448, 0xf0005, 0, 0, 0, 0, 0, 0x7ee18d48, 0x700016e9, 0x7000222c, 0x10, 0x700189fc, 0, 0, 0xc764, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) = 0
getpid() = 6507
sigaction(SIGILL, {0x70001c95, [], SA_RESTART}, {SIG_DFL}, 0) = 0
sigaction(SIGABRT, {0x70001c95, [], SA_RESTART}, {SIG_DFL}, 0) = 0
sigaction(SIGBUS, {0x70001c95, [], SA_RESTART}, {SIG_DFL}, 0) = 0
sigaction(SIGFPE, {0x70001c95, [], SA_RESTART}, {SIG_DFL}, 0) = 0
sigaction(SIGSEGV, {0x70001c95, [], SA_RESTART}, {SIG_DFL}, 0) = 0
sigaction(SIGSTKFLT, {0x70001c95, [], SA_RESTART}, {SIG_DFL}, 0) = 0
sigaction(SIGPIPE, {0x70001c95, [], SA_RESTART}, {SIG_DFL}, 0) = 0
stat64("/system/lib/liblog.so", {st_mode=S_IFREG|0644, st_size=13488, ...}) = 0
open("/system/lib/liblog.so", O_RDONLY|O_LARGEFILE) = 3
lseek(3, 0, SEEK_SET) = 0
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\f\20\0\000"..., 4096) = 4096
lseek(3, -8, SEEK_END) = 13480
read(3, "\0\0\274oPRE ", 8) = 8
mmap2(0x6fbc0000, 16384, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x6fbc0000
mmap2(0x6fbc0000, 10724, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x6fbc0000
mprotect(0x6fbc0000, 12288, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mmap2(0x6fbc3000, 368, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x3) = 0x6fbc3000
close(3) = 0
stat64("/system/lib/libc.so", {st_mode=S_IFREG|0644, st_size=243988, ...}) = 0
open("/system/lib/libc.so", O_RDONLY|O_LARGEFILE) = 3
lseek(3, 0, SEEK_SET) = 0
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\320\242"..., 4096) = 4096
lseek(3, -8, SEEK_END) = 243980
read(3, "\0\0\340oPRE ", 8) = 8
mmap2(0x6fe00000, 290816, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x6fe00000
mmap2(0x6fe00000, 230024, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x6fe00000
mprotect(0x6fe00000, 233472, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mmap2(0x6fe39000, 8544, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x39) = 0x6fe39000
mmap2(0x6fe3c000, 42280, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x6fe3c000
close(3) = 0
mprotect(0x6fe00000, 233472, PROT_READ|PROT_EXEC) = 0
getuid32() = 2000
geteuid32() = 0
open("/dev/null", O_RDWR|O_LARGEFILE) = 3
fcntl64(0, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(1, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(2, F_GETFL) = 0x2 (flags O_RDWR)
close(3) = 0
gettid() = 6507
syscall_983045(0x6fe43b10, 0, 0x40, 0, 0x6fe43c10, 0x7edf9000, 0x7ee18ba0, 0xf0005, 0, 0, 0, 0, 0, 0x7ee18b88, 0x6fe1fdc3, 0x6fe0d34c, 0x60000010, 0x6fe43b10, 0, 0, 0xc764, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) = 0
mmap2(NULL, 131072, PROT_READ, MAP_SHARED, 9, 0) = 0x2aaab000
open("/dev/urandom", O_RDONLY|O_LARGEFILE) = 3
read(3, "\345\347\3004", 4) = 4
close(3) = 0
stat64("/system/lib/libstdc++.so", {st_mode=S_IFREG|0644, st_size=5124, ...}) = 0
open("/system/lib/libstdc++.so", O_RDONLY|O_LARGEFILE) = 3
lseek(3, 0, SEEK_SET) = 0
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\234\10\0"..., 4096) = 4096
lseek(3, -8, SEEK_END) = 5116
read(3, "\0\0\320oPRE ", 8) = 8
mmap2(0x6fd00000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x6fd00000
mmap2(0x6fd00000, 2860, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x6fd00000
mprotect(0x6fd00000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mmap2(0x6fd01000, 232, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x1) = 0x6fd01000
close(3) = 0
mprotect(0x6fd00000, 4096, PROT_READ|PROT_EXEC) = 0
getuid32() = 2000
geteuid32() = 0
open("/dev/null", O_RDWR|O_LARGEFILE) = 3
fcntl64(0, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(1, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(2, F_GETFL) = 0x2 (flags O_RDWR)
close(3) = 0
stat64("/system/lib/libm.so", {st_mode=S_IFREG|0644, st_size=91056, ...}) = 0
open("/system/lib/libm.so", O_RDONLY|O_LARGEFILE) = 3
lseek(3, 0, SEEK_SET) = 0
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\240\34\0"..., 4096) = 4096
lseek(3, -8, SEEK_END) = 91048
read(3, "\0\0\300oPRE ", 8) = 8
mmap2(0x6fc00000, 94208, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x6fc00000
mmap2(0x6fc00000, 88856, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x6fc00000
mprotect(0x6fc00000, 90112, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mmap2(0x6fc16000, 204, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x16) = 0x6fc16000
close(3) = 0
mprotect(0x6fc00000, 90112, PROT_READ|PROT_EXEC) = 0
getuid32() = 2000
geteuid32() = 0
open("/dev/null", O_RDWR|O_LARGEFILE) = 3
fcntl64(0, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(1, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(2, F_GETFL) = 0x2 (flags O_RDWR)
close(3) = 0
mprotect(0x6fbc0000, 12288, PROT_READ|PROT_EXEC) = 0
getuid32() = 2000
geteuid32() = 0
open("/dev/null", O_RDWR|O_LARGEFILE) = 3
fcntl64(0, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(1, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(2, F_GETFL) = 0x2 (flags O_RDWR)
close(3) = 0
stat64("/system/lib/libcutils.so", {st_mode=S_IFREG|0644, st_size=59308, ...}) = 0
open("/system/lib/libcutils.so", O_RDONLY|O_LARGEFILE) = 3
lseek(3, 0, SEEK_SET) = 0
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0001\0\000"..., 4096) = 4096
lseek(3, -8, SEEK_END) = 59300
read(3, "\0\0\260oPRE ", 8) = 8
mmap2(0x6fb00000, 122880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x6fb00000
mmap2(0x6fb00000, 53584, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x6fb00000
mprotect(0x6fb00000, 57344, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mmap2(0x6fb0e000, 1076, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0xe) = 0x6fb0e000
mmap2(0x6fb0f000, 57732, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x6fb0f000
close(3) = 0
mprotect(0x6fb00000, 57344, PROT_READ|PROT_EXEC) = 0
getuid32() = 2000
geteuid32() = 0
open("/dev/null", O_RDWR|O_LARGEFILE) = 3
fcntl64(0, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(1, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(2, F_GETFL) = 0x2 (flags O_RDWR)
close(3) = 0
mprotect(0x8000, 69632, PROT_READ|PROT_EXEC) = 0
getuid32() = 2000
geteuid32() = 0
open("/dev/null", O_RDWR|O_LARGEFILE) = 3
fcntl64(0, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(1, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(2, F_GETFL) = 0x2 (flags O_RDWR)
close(3) = 0
getgroups32(64, [1003, 1004, 1007, 1011, 1015, 3001, 3002, 3003]) = 8
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2aacb000
mprotect(0x2aacb000, 4096, PROT_READ) = 0
fstat64(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 1), ...}) = 0
brk(0) = 0x1e000
brk(0x1e000) = 0x1e000
brk(0x1f000) = 0x1f000
mprotect(0x2aacb000, 4096, PROT_READ|PROT_WRITE) = 0
mprotect(0x2aacb000, 4096, PROT_READ) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
getuid32() = 2000
getgid32() = 2000
write(1, "uid=2000(shell) gid=2000(shell) "..., 145uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
) = 145
mprotect(0x2aacb000, 4096, PROT_READ|PROT_WRITE) = 0
mprotect(0x2aacb000, 4096, PROT_READ) = 0
munmap(0x2aacb000, 4096) = 0
exit_group(0) = ?
Process 6507 detached
#
Oh wow, so much fail.
OK first of all, the image is modded to allow your shell to be root. Running 'whoami' will (should) say uid 0 and you should have the # beside cursor.
If (like me) for some reason you ran this and your root apps don't work,
1) Connect to the phone with adb
2) mount the filesystem as R/W
3) install su to /system/bin chmod it to 6755
4) Download busybox from the market
5) type su
6) type whoami (should be unknown uid 0)
all "root" apps will use the su binary to become root so as long as what I said works then all root apps should work.
Yeah, I 've done that a few times already. Any other tips?
Sent from my SO-01B using XDA App
edude03 said:
Oh wow, so much fail.
OK first of all, the image is modded to allow your shell to be root. Running 'whoami' will (should) say uid 0 and you should have the # beside cursor.
If (like me) for some reason you ran this and your root apps don't work,
1) Connect to the phone with adb
2) mount the filesystem as R/W
3) install su to /system/bin chmod it to 6755
4) Download busybox from the market
5) type su
6) type whoami (should be unknown uid 0)
all "root" apps will use the su binary to become root so as long as what I said works then all root apps should work.
Click to expand...
Click to collapse
before saying all this, can I enquire if you have tried these steps on an X10 rooted using the method in question here. I mean I fully understand what "su" means and what "busybox" is for. So your point is?
Tried a third time, to really make sure I didn't rush anything. But even with a rooted system my uid is 10143. Rather odd since I can remount /system etc.
I'll get some sleep and take a fresh look later.
Sent from my SO-01B using XDA App
I though it was evident from the "(like me)" part that I had the same issue.
Yes this is what I did on my X10 rooted using the method outlined in the other thread.
edude03 said:
I though it was evident from the "(like me)" part that I had the same issue.
Yes this is what I did on my X10 rooted using the method outlined in the other thread.
Click to expand...
Click to collapse
And I thought the "I've tried that already" bit was self explanatory.
Sent from my SO-01B using XDA App
edude03 said:
I though it was evident from the "(like me)" part that I had the same issue.
Yes this is what I did on my X10 rooted using the method outlined in the other thread.
Click to expand...
Click to collapse
ok buddy, maybe I missed the (like me) part... but both ddewbofh and me have done essentially that. And our milage varies.
lrwxr-xr-x 1 0 2000 7 Feb 21 02:48 wipe -> toolbox
-rwxr-xr-x 1 0 2000 5592 Feb 21 02:48 wiperiface
-rwxr-xr-x 1 0 2000 5432 Feb 21 02:48 wlan_tool
-rwxr-xr-x 1 0 2000 61748 Feb 21 02:48 wmiconfig
-rwxr-xr-x 1 0 2000 205288 Feb 21 02:48 wpa_supplicant
lrwxrwxrwx 1 0 0 19 Jun 28 02:29 xargs -> /system/bin/busybox
lrwxrwxrwx 1 0 0 19 Jun 28 02:29 yes -> /system/bin/busybox
lrwxrwxrwx 1 0 0 19 Jun 28 02:29 zcat -> /system/bin/busybox
lrwxrwxrwx 1 0 0 19 Jun 28 02:29 zcip -> /system/bin/busybox
lrwxrwxrwx 1 0 0 7 Jun 28 00:40 zip -> busybox
#
#
# su
su
# whoami
whoami
whoami: unknown uid 2000
#
Click to expand...
Click to collapse
j4mm3r said:
ok buddy, maybe I missed the (like me) part... but both ddewbofh and me have done essentially that. And our milage varies.
Click to expand...
Click to collapse
my uid comes up as 10330 - I thought that this was strange...
My windows cmd skills are weak (linux only user for years...) but, well, here some quick instructions:
0. Download busybox (free) from Market (newer version than in root files)
1. download su-2.1-cd-unsecure-signed.zip from h t t p : / / f o r u m.xda-developers.com/showthread.php?t=682828
2. extract it into folder of your choosing
3. open up cmd (Win+R -> enter 'cmd')
4. Enter the following:
Code:
cd the-path-to-where-you-extracted-the-root-files/ROOT/Step4
adb install the-path-to-where-you-extracted-the-su-file\system\app\Superuser.apk
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push the-path-to-where-you-extracted-the-su-file\system\app\Superuser.apk /sdcard/Superuser.apk
adb push the-path-to-where-you-extracted-the-su-file\system\bin\su /sdcard/su
adb shell dd if=/sdcard/su of=/system/bin/su
adb shell dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk
adb shell reboot
After the phone rebooted, check if it worked (it did for me):
Code:
adb shell
whoami
su
whoami
the first whoami should give you a random number (10k something, I think?) when using su, you'll have to confirm the program to be allowed root access on your phone (something should pop up) and the second whoami should put out uid 0
hope that helps someone
Yeah root is in unconventional way atm, thats because it acts like this.
Will be fixed
Regards
Hi,
I want't adb on my desire. I use Leedroid and there is no adb binary. So I downloaded CM9 (and other) to rip it out. But all I get if I try to start the binary on my device is:
permission denied
(also with su)
Any advice?
Try switching to superuser (su) and then type:
Code:
chmod +x /bin/adb
I'm presuming it's an issue with permissions, that should sort it.
I did and get the following:
[1] + Stopped (signal) ./adb
and after one enter
[1] Segmentation fault ./adb
I have also tried to set chmod to 777.
htzeh said:
I did and get the following:
[1] + Stopped (signal) ./adb
and after one enter
[1] Segmentation fault ./adb
I have also tried to set chmod to 777.
Click to expand...
Click to collapse
Okay, try doing the same operation using adb on a computer.
If this doesn't work, rm the adb file using adb shell, and push your own to the same directory.
On the pc adb works, I can push, shell etc.
cyr0s said:
... rm the adb file using adb shell, and push your own to the same directory.
Click to expand...
Click to collapse
with the adb from the android-sdk (on pc):
1: Syntax error: "(" unexpected
I'm feeling like :silly:
Nobody there who has the adb binary on their phone?
Maybe the strace output can help (not for me )
adb3 is the "new" from pc, adb2 is the binary from CM9
Code:
adb shell "strace /system/sd/adb3"
execve("/system/sd/adb3", ["/system/sd/adb3"], [/* 13 vars */]) = -1 ENOEXEC (Exec format error)
write(2, "strace: exec", 12strace: exec) = 12
write(2, ": ", 2: ) = 2
write(2, "Exec format error", 17Exec format error) = 17
write(2, "\n", 1
) = 1
SYS_248(0x1, 0xafd3af7f, 0xf73b60f4, 0xf73b60f4, 0x1 <unfinished ... exit status 1>
Code:
adb shell "strace /system/sd/adb2"
execve("/system/sd/adb2", ["/system/sd/adb2"], [/* 13 vars */]) = 0
syscall_983045(0xb0011a4c, 0x1, 0xb0012574, 0, 0xb0010d90, 0xb0009468, 0xbebfeb80, 0xf0005, 0xbebfeb8c, 0xb0007268, 0xb000726f, 0xb0007280, 0, 0xbebfeb20, 0xb0004e21, 0xb000121c, 0x80000010, 0xb0011a4c, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) = 0
getpid() = 9707
sigaction(SIGILL, {0xb000586d, [], SA_RESTART}, {SIG_DFL}, 0xb0009468) = 0
sigaction(SIGABRT, {0xb000586d, [], SA_RESTART}, {SIG_DFL}, 0) = 0
sigaction(SIGBUS, {0xb000586d, [], SA_RESTART}, {SIG_DFL}, 0) = 0
sigaction(SIGFPE, {0xb000586d, [], SA_RESTART}, {SIG_DFL}, 0) = 0
sigaction(SIGSEGV, {0xb000586d, [], SA_RESTART}, {SIG_DFL}, 0) = 0
sigaction(SIGSTKFLT, {0xb000586d, [], SA_RESTART}, {SIG_DFL}, 0) = 0
sigaction(SIGPIPE, {0xb000586d, [], SA_RESTART}, {SIG_DFL}, 0) = 0
getuid32() = 0
geteuid32() = 0
getgid32() = 0
getegid32() = 0
--- SIGSEGV (Segmentation fault) @ 0 (15d58) ---
sigaction(SIGUSR1, {SIG_IGN}, {SIG_DFL}, 0) = 0
SYS_224(0, 0xbebfe7c0, 0xbebfe7c0, 0) = 9707
socket(PF_UNIX, SOCK_STREAM, 0) = 3
connect(3, {sa_family=AF_UNIX, [email protected]:debuggerd}, 20) = 0
write(3, "�%\0\0", 4) = 4
--- SIGCONT (Continue) @ 0 (0) ---
read(3, "", 1) = 0
close(3) = 0
sigaction(SIGSEGV, {SIG_IGN}, {0xb000586d, [], SA_RESTART}, 0) = 0
sigreturn() = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (15d58) ---
+++ killed by SIGSEGV +++