NSS question

2008-04-15 Thread Zane C.B.
The only documentation I can really find for writing NSS stuff is the stuff for glibc. Any differences or the like I need to be aware of in regards to FreeBSD? http://www.gnu.org/software/libtool/manual/libc/Name-Service-Switch.html#Name-Service-Switch _

Re: "visualize" kernel memory allocations

2008-04-15 Thread Antoine Brodin
On Tue, Apr 15, 2008 at 2:37 PM, Antoine Brodin <[EMAIL PROTECTED]> wrote: > On Mon, Apr 14, 2008 at 9:18 PM, Volker <[EMAIL PROTECTED]> wrote: > > Hi hackers! > > > > I need to hunt kernel memory allocations done by a kld. Unfortunately > > the kld in question is a blob, no access to source

Re: "visualize" kernel memory allocations

2008-04-15 Thread Antoine Brodin
On Mon, Apr 14, 2008 at 9:18 PM, Volker <[EMAIL PROTECTED]> wrote: > Hi hackers! > > I need to hunt kernel memory allocations done by a kld. Unfortunately > the kld in question is a blob, no access to source code, so I need to > check for kmem_alloc() + kmem_malloc() + kmem_free() and print > i

Re: "visualize" kernel memory allocations

2008-04-15 Thread Joerg Sonnenberger
On Tue, Apr 15, 2008 at 08:06:28PM +1000, Peter Jeremy wrote: > About all I can suggest is working out the return address and finding > which module that exists within. That doesn't sound particularly nice. Search gcc's info file for __builtin_return_address for the first part. Joerg ___

Re: "visualize" kernel memory allocations

2008-04-15 Thread Peter Jeremy
On Mon, Apr 14, 2008 at 09:18:31PM +0200, Volker wrote: >From within these functions, I need to get the name (or an ID) of the >module trying to allocate memory (and display that or - better - filter >some allocations out). About all I can suggest is working out the return address and finding whic

Re: "visualize" kernel memory allocations

2008-04-15 Thread Robert Watson
On Mon, 14 Apr 2008, Volker wrote: I need to hunt kernel memory allocations done by a kld. Unfortunately the kld in question is a blob, no access to source code, so I need to check for kmem_alloc() + kmem_malloc() + kmem_free() and print information from there to the console screen. From w