abe wrote: > On Thu, Oct 10, 2002 at 03:50:47PM -0700, Terry Lambert wrote: > > You should be able to find out the C code at assembly code offset > > 0x172, assuming you created your kernel with "config -g", and you ******* > > compiled the ipfw statically into the kernel, instead of loading **************************************************************** > > it as a module. ************** > > > > Assuming this is the case, to do that, go to the directory you > > compiled the kernel in, and run: > > > > gdb -k kernel.debug > > list *add_dyn_rule+0x172 > > (kgdb) list *add_dyn_rule+0x172 > No source file for address 0xc021e5d6 > (kgdb)
Not to be emphatic, or anything, but IPFW has to be static. There is voodoo you can use to make it know about loaded modules, but I'll be damned if I know what it is (again, I refer you to the handbook). 8-). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message