Hi Stefan,

On 2/9/11, Stefan <[email protected]> wrote:
> Hey guys,
>
> my question is following:
>
> How can I "read" the boot.strace file to find
> where my boot sequence has a failure?
>
> I don't want to post the whole 9000 lines of
> boot strace, but here is a  the last part of if:
>
> 18:32:13.115194 writev(3, [{"\3", 1}, {"dalvikvm\0", 9}, {"GC freed
> 127 objects / 5064 byte"..., 44}], 3) = 54
> 18:32:13.123145 open("/proc/self/cmdline", O_RDONLY|O_LARGEFILE) = 18
> 18:32:13.124556 read(18, "zygote\0/bin/app_process\0-Xzygote"..., 127)
> = 76
> 18:32:13.126147 close(18)               = 0
> 18:32:13.127144 writev(5, [{"!N\0\0", 4}, {"\3", 1}, {"\4\1=S\6togyz
> \1&8KFš\202\177\200\1&8KFš\202OÈ\1\224Vp"..., 37}], 3) = 42
> 18:32:13.129144 msgget(0x1, 0xbedc9a58, 0x4108e468, 0x4108e4a0) = 0
> 18:32:13.130117 msgget(0x3, 0xbedc9a58, 0xad080c00, 0) = 0
> 18:32:13.131133 msgget(0x1, 0xbedc98f8, 0, 0xa9d214e8) = 0
> 18:32:13.132165 msgget(0x1, 0xbedc9a58, 0x4108a670, 0x4108a6e0) = 0
> 18:32:13.133133 msgget(0x3, 0xbedc9a58, 0xad080c00, 0) = 0
> 18:32:13.134151 msgget(0x1, 0xbedc9a58, 0x4108b0dc, 0x4108b148) = 0
> 18:32:13.135237 msgget(0x3, 0xbedc9a58, 0xad080c00, 0) = 0
> 18:32:13.136260 msgget(0x1, 0xbedc9a58, 0x4108a670, 0x4108a6e0) = 0
> 18:32:13.137236 msgget(0x3, 0xbedc9a58, 0xad080c00, 0) = 0
> 18:32:13.138265 msgget(0x1, 0xbedc9a58, 0x4108b0dc, 0x4108b148) = 0
> 18:32:13.139522 msgget(0x3, 0xbedc9a58, 0xad080c00, 0) = 0
> 18:32:13.140550 msgget(0x1, 0xbedc99f0, 0xad080f48, 0xe1f89969) = 0
> 18:32:13.141539 getpriority(PRIO_PROCESS, 0) = 20
> 18:32:13.142513 open("/dev/ashmem", O_RDWR|O_LARGEFILE) = 18
> 18:32:13.143763 ioctl(18, 0x41007701, 0xbedc9874) = 0
> 18:32:13.144863 ioctl(18, 0x40047703, 0x1a4000) = 0
> 18:32:13.145833 mmap2(NULL, 1720320, PROT_READ|PROT_WRITE,
> MAP_PRIVATE, 18, 0) = 0x42e1f000
> 18:32:13.146925 close(18)               = 0
> 18:32:13.147961 open("/dev/ashmem", O_RDWR|O_LARGEFILE) = 18
> 18:32:13.149210 ioctl(18, 0x41007701, 0xbedc870c) = 0
> 18:32:13.150172 ioctl(18, 0x40047703, 0x40000) = 0
> 18:32:13.151137 mmap2(NULL, 262144, PROT_READ|PROT_WRITE, MAP_PRIVATE,
> 18, 0) = 0x42742000
> 18:32:13.152236 close(18)               = 0
> 18:32:13.233086 recv(-1391980656, 0x1, 1, 0) = 0
> 18:32:13.238503 munmap(0x426b8000, 262144) = 0
> 18:32:13.239736 munmap(0x42e1f000, 1720320) = 0
> 18:32:13.240979 msgget(0x1, 0xbedc99e8, 0xad080c00, 0x34c) = 0
> 18:32:13.241978 recv(-1391980656, 0x1, 1, 0) = 0
> 18:32:13.243139 recv(-1391980804, 0x1, 2147483647, 0) = 0
> 18:32:13.244317 msgget(0x1, 0xbedc99f0, 0xad080ef8, 0x2710) = 0
> 18:32:13.245495 writev(3, [{"\3", 1}, {"dalvikvm\0", 9}, {"GC freed 14
> objects / 496 bytes "..., 42}], 3) = 52
> 18:32:13.253381 open("/proc/self/cmdline", O_RDONLY|O_LARGEFILE) = 18
> 18:32:13.254963 read(18, "zygote\0/bin/app_process\0-Xzygote"..., 127)
> = 76
> 18:32:13.256506 close(18)               = 0
> 18:32:13.257569 writev(5, [{"!N\0\0", 4}, {"\3", 1}, {"\4\1ðq\6togyz
> \1&8KFš\202\16\200\1&8KFš\202OÈ\1\224Vp"..., 37}], 3) = 42
> 18:32:13.259636 msgget(0x1, 0xbedc9a58, 0x4108e468, 0x4108e4a0) = 0
> 18:32:13.260658 msgget(0x3, 0xbedc9a58, 0xad080c00, 0) = 0
> 18:32:13.261734 msgget(0x1, 0xbedc98f8, 0, 0xa9d214e8) = 0
> 18:32:13.262990 writev(3, [{"\4", 1}, {"Zygote\0", 7}, {"Accepting
> command socket connect"..., 37}], 3) = 45
> 18:32:13.271040 select(11, [10], NULL, NULL, NULL
>
>
> Maybe one of you knows this problem?
>

Normally we can check it just looking the syscall return number. When
you get an error it will return a negative number, then we can verify
which ERRNO is it, i.e.:
https://acassis.wordpress.com/2009/10/29/creating-an-error-number-table/

In your log there is no apparent error, just use "adb logcat" to get more info.

BR,

Alan

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to