On Tue, 27 Feb 2001, John Baldwin wrote: > Ok. It may be that we are overflowing the kernel stack and corrupting the pcb > in the process. One idea atm is to move the pcb off of the stack (since it > stores persistent data it's a bad place for it anyways) and to add a red zone > at the bottom of the stack to catch overflows. Most of the pcb actually has the same persistence as the kernel stack (both mainly store the process's context while the process is in the kernel). But it is silly to put the pcb below the stack instead of above it. Perhaps the idea is to get a panic sooner when something is corrupted. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- make kernel failure: pecoff: machine/lock.h Leif Neland
- RE: make kernel failure: pecoff: machine/lock.h John Baldwin
- Re: make kernel failure: pecoff: machine/lock.h Gary Jennejohn
- Re: make kernel failure: pecoff: machine/lock... Leif Neland
- Re: make kernel failure: pecoff: machine/... John Baldwin
- Re: make kernel failure: pecoff: mac... Leif Neland
- Re: make kernel failure: pecoff:... John Baldwin
- Re: make kernel failure: pecoff: mac... Bruce Evans
- Re: make kernel failure: pecoff:... Julian Elischer
- Re: make kernel failure: pec... Bruce Evans
- Re: make kernel failure: pec... Julian Elischer
- Re: make kernel failure: pecoff:... John Baldwin
- Re: make kernel failure: pec... Bruce Evans
- Re: make kernel failure: pecoff: machine/... Edwin Culp
- Re: make kernel failure: pecoff: machine/... Warner Losh
- Re: make kernel failure: pecoff: machine/lock.h David O'Brien
- Re: make kernel failure: pecoff: machine/lock.h Warner Losh
- Re: make kernel failure: pecoff: machine/lock.h Warner Losh