On 3/5/07, Rick Olson <[EMAIL PROTECTED]> wrote:
I'm really not sure which list to post this to, and this is my first
post on any of the official FreeBSD mailing lists, so pardon my
ignorance. This was a tossup between arch & hackers.
A long time ago, way back in May of 2005, there was a bug/ch
On 2007-Mar-05 15:31:09 -0500, Dave Arsenault <[EMAIL PROTECTED]> wrote:
>How would I go about debugging a LKM. I am currently working on a simple
>kernel module that overwrites the open() syscall and sends the output
>through a parsing routine.
Have a read of /usr/src/tools/debugscripts/README
I
I'm really not sure which list to post this to, and this is my first
post on any of the official FreeBSD mailing lists, so pardon my
ignorance. This was a tossup between arch & hackers.
A long time ago, way back in May of 2005, there was a bug/change-request
posted by a Tim H. regarding incre
On Tue, Mar 06, 2007 at 12:15:56AM +, Robert Watson wrote:
> On Sun, 4 Mar 2007, Divacky Roman wrote:
>
> >I looked at where Giant is held in the kernel and I found these
> >interesting things:
> >
> >1) in fs/fifofs/fifo_vnops.c we lock Giant when calling
> >sorecieve()/sosend() this is a b
On Sun, 4 Mar 2007, Divacky Roman wrote:
I looked at where Giant is held in the kernel and I found these interesting
things:
1) in fs/fifofs/fifo_vnops.c we lock Giant when calling sorecieve()/sosend()
this is a bandaid for fixing a race that doesnt have to exist anymore. ie.
it needs some t
How would I go about debugging a LKM. I am currently working on a simple
kernel module that overwrites the open() syscall and sends the output
through a parsing routine.
I've read many articles talking about using the (gdb) add-symbol-file
lkm.ko and in fact that works but as far as I know I can
6 matches
Mail list logo
