Re: Ability to tell the difference between normal and syscall traps

Kostik Belousov yazmış: > On Sat, May 08, 2010 at 02:15:09PM +0300, Ali Polatel wrote: > > Does FreeBSD's ptrace have a way to tell the difference between normal > > traps and those caused by a system call? > > > > On Linux? this is possible by passing PTRACE_O_TRACESYSGOOD option to the > > ptrac

Re: How to get data from kernel module ?

Lukáš Czerner wrote: Hi, I am creating a kernel module and I need to get some information from that module. I can do this with ioctl and pass the data to the user space but it seems a bit unpractical to me, because I do not know the amount of the data - it can differ. I do not know of any way t

Re: nginx + passenger = segv in _rtld_error on restart onFreeBSD8.0?

Thanks Matt most appreciated! - Original Message - From: "Matt Reimer" Steve, The patch for PR 144061 works for us. http://lists.freebsd.org/pipermail/freebsd-hackers/2010-February/030741.html http://www.freebsd.org/cgi/query-pr.cgi?pr=144061 =

Re: nginx + passenger = segv in _rtld_error on restart on FreeBSD 8.0?

As you may have guessed by my last reply no we didn't we had to revert to apache + passenger, but seems you've found a fix anyway. Out of interest what lead you to the close race condition PR as a potential fix? - Original Message - From: "Matt Reimer" Steve, Did you figure this out?

Re: Ability to tell the difference between normal and syscall traps

Kostik Belousov yazmış: > On Sat, May 08, 2010 at 02:15:09PM +0300, Ali Polatel wrote: > > Does FreeBSD's ptrace have a way to tell the difference between normal > > traps and those caused by a system call? > > > > On Linux? this is possible by passing PTRACE_O_TRACESYSGOOD option to the > > ptrac

Re: Ability to tell the difference between normal and syscall traps

On Sat, May 08, 2010 at 02:15:09PM +0300, Ali Polatel wrote: > Does FreeBSD's ptrace have a way to tell the difference between normal > traps and those caused by a system call? > > On Linux? this is possible by passing PTRACE_O_TRACESYSGOOD option to the > ptrace request PTRACE_SETOPTIONS which ma

Ability to tell the difference between normal and syscall traps

Does FreeBSD's ptrace have a way to tell the difference between normal traps and those caused by a system call? On Linux¹ this is possible by passing PTRACE_O_TRACESYSGOOD option to the ptrace request PTRACE_SETOPTIONS which makes the kernel set bit 7 in the syscall number when delivering system c