"2838c9682aadaf8db1db7f32bbcb5953b141e999" (history) in projects: freebsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched hist:"2838 c9682aadaf8db1db7f32bbcb5953b141e999" (Results 1 – 8 of 8) sorted by relevance

/freebsd/sys/amd64/include/
H A D	cpufunc.h	diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause. diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause.
/freebsd/sys/amd64/amd64/
H A D	exception.S	diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause. diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause.
H A D	fpu.c	diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause. diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause.
H A D	trap.c	diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause. diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause.
H A D	machdep.c	diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause. diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause.
/freebsd/sys/kern/
H A D	subr_trap.c	diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause. diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause.
/freebsd/sys/i386/i386/
H A D	trap.c	diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause. diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause.
H A D	machdep.c	diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause. diff 2838c9682aadaf8db1db7f32bbcb5953b141e999 Tue Dec 19 15:30:50 CET 1995 David Greenman <dg@FreeBSD.org> Implemented a (sorely needed for years) double fault handler to catch stack overflows. It sure would be nice if there was an unmapped page between the PCB and the stack (and that the size of the stack was configurable!). With the way things are now, the PCB will get clobbered before the double fault handler gets control, making somewhat of a mess of things. Despite this, it is still fairly easy to poke around in the overflowed stack to figure out the cause.