Re: Weird truss output

2008-12-04 Thread Vlad GALU
On Thu, Dec 4, 2008 at 12:55 AM, Dan Nelson <[EMAIL PROTECTED]> wrote: > In the last episode (Dec 03), Vlad GALU said: >> On Wed, Dec 3, 2008 at 8:56 PM, Dan Nelson <[EMAIL PROTECTED]> wrote: >> [...] >> >> Am I doing something wrong? I've applied the full diff, rebuilt >> truss, now I get this:

Re: Weird truss output

2008-12-03 Thread Dan Nelson
In the last episode (Dec 03), Vlad GALU said: > On Wed, Dec 3, 2008 at 8:56 PM, Dan Nelson <[EMAIL PROTECTED]> wrote: > [...] > > Am I doing something wrong? I've applied the full diff, rebuilt > truss, now I get this: > -- cut here -- > [EMAIL PROTECTED] / # truss -p 52731 > SIGNAL 17 (SIGSTOP)

Re: Weird truss output

2008-12-03 Thread Vlad GALU
On Wed, Dec 3, 2008 at 8:56 PM, Dan Nelson <[EMAIL PROTECTED]> wrote: [...] Am I doing something wrong? I've applied the full diff, rebuilt truss, now I get this: -- cut here -- [EMAIL PROTECTED] / # truss -p 52731 SIGNAL 17 (SIGSTOP) -- UNKNOWN SYSCALL 1048535 -- -- UNKNOWN SYSCALL 1048496 -

Re: Weird truss output

2008-12-03 Thread Dan Nelson
In the last episode (Dec 03), Dan Nelson said: > It looks like there's some other problem where truss either drops a > syscall event, or puts some status fields into the wrong thread's > structure. It seems to happen when two threads call blocking > syscalls, and when they return, truss gets confu

Re: Weird truss output

2008-12-03 Thread Marius Nünnerich
On Wed, Dec 3, 2008 at 6:08 PM, Dan Nelson <[EMAIL PROTECTED]> wrote: > In the last episode (Dec 03), Vlad GALU said: >> On Wed, Dec 3, 2008 at 5:23 PM, Dan Nelson <[EMAIL PROTECTED]> wrote: >> > In the last episode (Dec 03), Vlad GALU said: >> >> I'm running a statically linked binary, which I've

Re: Weird truss output

2008-12-03 Thread Vlad GALU
On Wed, Dec 3, 2008 at 7:08 PM, Dan Nelson <[EMAIL PROTECTED]> wrote: > In the last episode (Dec 03), Vlad GALU said: >> On Wed, Dec 3, 2008 at 5:23 PM, Dan Nelson <[EMAIL PROTECTED]> wrote: >> > In the last episode (Dec 03), Vlad GALU said: >> >> I'm running a statically linked binary, which I've

Re: Weird truss output

2008-12-03 Thread Dan Nelson
In the last episode (Dec 03), Vlad GALU said: > On Wed, Dec 3, 2008 at 5:23 PM, Dan Nelson <[EMAIL PROTECTED]> wrote: > > In the last episode (Dec 03), Vlad GALU said: > >> I'm running a statically linked binary, which I've built inside a > >> jail. The jail's libc & co are in sync with the host's.

Re: Weird truss output

2008-12-03 Thread Dan Nelson
In the last episode (Dec 03), Vlad GALU said: > I'm running a statically linked binary, which I've built inside a > jail. The jail's libc & co are in sync with the host's. Truss then > shows this: > > -- cut here -- > -- UNKNOWN SYSCALL 1048532 -- > -- UNKNOWN SYSCALL 1048532 -- Is this a threade

Re: Weird truss output

2008-12-03 Thread Vlad GALU
On Wed, Dec 3, 2008 at 5:23 PM, Dan Nelson <[EMAIL PROTECTED]> wrote: > In the last episode (Dec 03), Vlad GALU said: >> I'm running a statically linked binary, which I've built inside a >> jail. The jail's libc & co are in sync with the host's. Truss then >> shows this: >> >> -- cut here -- >> --

Weird truss output

2008-12-03 Thread Vlad GALU
Hello, I'm running a statically linked binary, which I've built inside a jail. The jail's libc & co are in sync with the host's. Truss then shows this: -- cut here -- -- UNKNOWN SYSCALL 1048532 -- -- UNKNOWN SYSCALL 1048532 -- -- UNKNOWN SYSCALL 1048524 -- -- UNKNOWN SYSCALL 1048516 -- -- UNKNOWN