On Thu, Sep 08, 2005 at 11:04:12AM +0200, Marc Olzheim wrote: > On Thu, Sep 08, 2005 at 12:43:36AM -0400, Kris Kennaway wrote: > > db> wh > > Tracing pid 23098 tid 100263 td 0xc92e4af0 > > kdb_enter(c07060af,0,c070c9b3,f7d14bc8,c92e4af0) at kdb_enter+0x30 > > panic(c070c9b3,0,ffffffff,3f5,c0709939) at panic+0x13e > > soreceive(c9be5b20,0,f7d14cb4,0,0,f7d14c30,4000) at soreceive+0x1cd > > fifo_read_f(c8dc17e0,f7d14cb4,c5c88000,0,c92e4af0) at fifo_read_f+0x70 > > dofileread(c92e4af0,3,c8dc17e0,f7d14cb4,ffffffff) at dofileread+0x96 > > kern_readv(c92e4af0,3,f7d14cb4,bfbfdb87,1) at kern_readv+0x61 > > read(c92e4af0,f7d14d04,c,422,3) at read+0x4f > > syscall(3b,3b,3b,bfbfdbc0,809b440) at syscall+0x295 > > Xint0x80_syscall() at Xint0x80_syscall+0x1f > > --- syscall (3, FreeBSD ELF32, read), eip = 0x807d183, esp = 0xbfbfdb6c, > > ebp = 0xbfbfdb88 --- > > db> > > What kind ot kern_readv() is that ? Prototype of mine is: > > int kern_readv(struct thread *td, int fd, struct uio *auio); > > Or does the debugger garble something ?
Late followup, but the debugger has to guess at how many arguments are in use by the function, so it sometimes displays too many. Kris
pgpkqXQHn32Pu.pgp
Description: PGP signature
