Hi folks, One of my colleages met a panic at boot today,after he modified some kernel code for tcp.The panic occurrs in 'unix' module,at which point tcp is initialized.He would like to set a breakpoint at tcp init routine for debugging, but as unix is loaded immediately after kmdb, we don't have the chance to invoke kmdb at boot to set the breakpoint before tcp init function is called,thus the panic happens every time. Is there a way to set up a breakpoint early at boot such as this? If this is not the case,which is the best way for debugging this kind of problems?
Thanks, Zhijun
