d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Corrected a typo in a comment.

Browse Source
This commit is contained in:
dg 1995-12-19 14:47:41 +00:00
parent 95d4407d25
commit a82978cb5f
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
sys/amd64/amd64/trap.c
View File

@ -35,7 +35,7 @@
* SUCH DAMAGE.
*
* from: @(#)trap.c 7.4 (Berkeley) 5/13/91
* $Id: trap.c,v 1.66 1995/12/14 14:35:36 peter Exp $
* $Id: trap.c,v 1.67 1995/12/19 14:30:28 davidg Exp $
*/
/*
@ -765,7 +765,7 @@ trap_fatal(frame)
* XXX Note that the current PTD gets replaced by IdlePTD when the
* task switch occurs. This means that the stack that was active at
* the time of the double fault is not available at <kstack> unless
* the machine was idlewhen the double fault occurred. This downside
* the machine was idle when the double fault occurred. The downside
* of this is that "trace <ebp>" in ddb won't work.
*/
void

4
sys/i386/i386/trap.c
View File

@ -35,7 +35,7 @@
* SUCH DAMAGE.
*
* from: @(#)trap.c 7.4 (Berkeley) 5/13/91
* $Id: trap.c,v 1.66 1995/12/14 14:35:36 peter Exp $
* $Id: trap.c,v 1.67 1995/12/19 14:30:28 davidg Exp $
*/
/*
@ -765,7 +765,7 @@ trap_fatal(frame)
* XXX Note that the current PTD gets replaced by IdlePTD when the
* task switch occurs. This means that the stack that was active at
* the time of the double fault is not available at <kstack> unless
* the machine was idlewhen the double fault occurred. This downside
* the machine was idle when the double fault occurred. The downside
* of this is that "trace <ebp>" in ddb won't work.
*/
void

4
sys/kern/subr_trap.c
View File

@ -35,7 +35,7 @@
* SUCH DAMAGE.
*
* from: @(#)trap.c 7.4 (Berkeley) 5/13/91
* $Id: trap.c,v 1.66 1995/12/14 14:35:36 peter Exp $
* $Id: trap.c,v 1.67 1995/12/19 14:30:28 davidg Exp $
*/
/*
@ -765,7 +765,7 @@ trap_fatal(frame)
* XXX Note that the current PTD gets replaced by IdlePTD when the
* task switch occurs. This means that the stack that was active at
* the time of the double fault is not available at <kstack> unless
* the machine was idlewhen the double fault occurred. This downside
* the machine was idle when the double fault occurred. The downside
* of this is that "trace <ebp>" in ddb won't work.
*/
void