[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120719185603.GA6204@albatros>
Date: Thu, 19 Jul 2012 22:56:03 +0400
From: Vasily Kulikov <segoon@...nwall.com>
To: owl-dev@...ts.openwall.com
Subject: Re: strace with restart_syscall output
On Thu, Jul 19, 2012 at 22:44 +0400, Dmitry V. Levin wrote:
> On Thu, Jul 19, 2012 at 10:11:17PM +0400, Vasily Kulikov wrote:
> > root@...alhost:~ # strace -d /bin/true
> > ptrace_setoptions = 0x11
> > new tcb for pid 1302, active tcbs:1
> > [wait(0x137f) = 1302] WIFSTOPPED,sig=SIGSTOP
> > pid 1302 has TCB_STARTUP, initializing it
> > setting opts 11 on pid 1302
> > ignored SIGSTOP on pid 1302
> > [wait(0x857f) = 1302] WIFSTOPPED,sig=133
> > restart_syscall(<... resuming interrupted call ...> [wait(0x4057f) = 1302] WIFSTOPPED,sig=SIGTRAP,PTRACE_EVENT_EXEC
> > [wait(0x857f) = 1302] WIFSTOPPED,sig=133
> > ) = 0
> > [wait(0x857f) = 1302] WIFSTOPPED,sig=133
> > restart_syscall(<... resuming interrupted call ...> [wait(0x0000) = 1302] WIFEXITED,exitcode=0
> > <unfinished ...>
> > +++ exited with 0 +++
> > dropped tcb for pid 1302, 0 remain
> > root@...alhost:~ #
>
> Either PTRACE_GETREGS doesn't work or struct pt_regs defined in
> <asm/ptrace.h> unexpectedly changed so much that old pt_regs.orig_eax
> offset is no longer valid. Have you tried to rebuild strace with those
> kernel headers that match the kernel you test?
Indeed, installing rebuilded strace does help. Thank you!
Now all userspace seems to work.
--
Vasily
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
