On Aug 8, 1:35 pm, Chris Stratton <[email protected]> wrote: > On Monday, August 8, 2011 2:31:07 PM UTC-4, michael wrote: > > > I could trace the system call of one specific process in the > > emulator, but when I want to filter out the system calls with specific > > limitations, llike -e =trace=network. It does not work and gave me > > that error > > Well you could try doing it without that option, it narrow down the output > with grep or something > > > > Its possible you are on a build with a broken strace, or tried to move a > > > copy from a build that had it to a not-quite-compatible build that > > didn't? > > > strace depends on the syscall numbers and hence kernel version. > > > what do you mean broken strace? it works well except the opitions -e > > I was thinking more generally broken, but this sounds broken too. If you > want to have lots of fun, you can try running strace under gdbserver or > otherwise figuring out why it fails and then try to fix it in the source. > > You could also check the sources on android.git.kernel.org and see if there > have been any recent changes to strace before/after your version > > I suppose its also possible that it's not strace crashing but the process > you are monitoring, perhaps somehow due to being ptrace'd > > FWIW I just succesfully ran an strace -p [browser pid] -e trace=network on > my phone
you ran it in your real device? I check all the processes in the emulator, all do not work. weird thing. what is the version of your phone's OS? -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-security-discuss?hl=en.
