On Thursday 17 November 2011 17:36:36 Igal Sokolov wrote:
> I am using strace on MIPS. During the tracing I get plenty of
> 
> [pid  1435] syscall_834107236(0x6ba, 0x393a9d54, 0xffffffff, 0x1,
> 0xbd0000, 0, 0x3937b900, 0x3937b900, 0x1, 0x3939d000, 0x8731fc,
> 0x31f12fc8, 0x31f13190, 0x2c8482d0, 0, 0xbd46d0, 0x8ebfc8, 0x32,
> 0x7d0f00, 0x133, 0xb38b2f5e, 0x31f12e70, 0x22, 0x31f13118, 0x7d0f00,
> 0x8ec020, 0x3937b900, 0, 0, 0x2c76a000, 0x22, 0xbd46d0) = -1 (errno
> 834107236)

looks like your strace or kernel ptrace is screwed up.  you probably want to 
fix that anyways ...

> Is there any way to filter these syscalls without rebuilding strace itself

use the -e option like:
        strace -e'!open,close,write,read' ls

for more info, read the strace(1) manpage
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Strace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/strace-devel
  • syscall_ Igal Sokolov
    • Re: syscall_ Mike Frysinger

Reply via email to