0ca74ba0d8
now makes use of lockmgr(). Since we broke into the debugger from an interrupt, we don't have a curproc, so when lockmgr() tries to find our PID it barfs, causing another break into DDB which then calls the mysterious code that calls lockmgr() again..... So set doing_shutdown while we're in DDB so lockmgr ignores locks. |
||
|---|---|---|
| .. | ||
| adosfs | ||
| arch | ||
| coda | ||
| compat | ||
| conf | ||
| crypto | ||
| ddb | ||
| dev | ||
| filecorefs | ||
| gdbscripts | ||
| ipkdb | ||
| isofs | ||
| kern | ||
| lib | ||
| lkm | ||
| miscfs | ||
| msdosfs | ||
| net | ||
| netatalk | ||
| netccitt | ||
| netinet | ||
| netinet6 | ||
| netiso | ||
| netkey | ||
| netnatm | ||
| netns | ||
| nfs | ||
| ntfs | ||
| stand | ||
| sys | ||
| ufs | ||
| uvm | ||
| Makefile | ||