Searched hist:131905 (Results 1 - 8 of 8) sorted by relevance

/freebsd-10.2-release/sys/sparc64/include/
H A Dpcb.hdiff 131905 Sat Jul 10 19:56:00 MDT 2004 marcel Implement makectx(). The makectx() function is used by KDB to create
a PCB from a trapframe for purposes of unwinding the stack. The PCB
is used as the thread context and all but the thread that entered the
debugger has a valid PCB.
This function can also be used to create a context for the threads
running on the CPUs that have been stopped when the debugger got
entered. This however is not done at the time of this commit.
/freebsd-10.2-release/sys/ia64/include/
H A Dpcb.hdiff 131905 Sat Jul 10 19:56:00 MDT 2004 marcel Implement makectx(). The makectx() function is used by KDB to create
a PCB from a trapframe for purposes of unwinding the stack. The PCB
is used as the thread context and all but the thread that entered the
debugger has a valid PCB.
This function can also be used to create a context for the threads
running on the CPUs that have been stopped when the debugger got
entered. This however is not done at the time of this commit.
/freebsd-10.2-release/sys/i386/include/
H A Dpcb.hdiff 131905 Sat Jul 10 19:56:00 MDT 2004 marcel Implement makectx(). The makectx() function is used by KDB to create
a PCB from a trapframe for purposes of unwinding the stack. The PCB
is used as the thread context and all but the thread that entered the
debugger has a valid PCB.
This function can also be used to create a context for the threads
running on the CPUs that have been stopped when the debugger got
entered. This however is not done at the time of this commit.
/freebsd-10.2-release/sys/amd64/include/
H A Dpcb.hdiff 131905 Sat Jul 10 19:56:00 MDT 2004 marcel Implement makectx(). The makectx() function is used by KDB to create
a PCB from a trapframe for purposes of unwinding the stack. The PCB
is used as the thread context and all but the thread that entered the
debugger has a valid PCB.
This function can also be used to create a context for the threads
running on the CPUs that have been stopped when the debugger got
entered. This however is not done at the time of this commit.
/freebsd-10.2-release/sys/sparc64/sparc64/
H A Dmachdep.cdiff 131905 Sat Jul 10 19:56:00 MDT 2004 marcel Implement makectx(). The makectx() function is used by KDB to create
a PCB from a trapframe for purposes of unwinding the stack. The PCB
is used as the thread context and all but the thread that entered the
debugger has a valid PCB.
This function can also be used to create a context for the threads
running on the CPUs that have been stopped when the debugger got
entered. This however is not done at the time of this commit.
/freebsd-10.2-release/sys/ia64/ia64/
H A Dmachdep.cdiff 131905 Sat Jul 10 19:56:00 MDT 2004 marcel Implement makectx(). The makectx() function is used by KDB to create
a PCB from a trapframe for purposes of unwinding the stack. The PCB
is used as the thread context and all but the thread that entered the
debugger has a valid PCB.
This function can also be used to create a context for the threads
running on the CPUs that have been stopped when the debugger got
entered. This however is not done at the time of this commit.
/freebsd-10.2-release/sys/i386/i386/
H A Dmachdep.cdiff 131905 Sat Jul 10 19:56:00 MDT 2004 marcel Implement makectx(). The makectx() function is used by KDB to create
a PCB from a trapframe for purposes of unwinding the stack. The PCB
is used as the thread context and all but the thread that entered the
debugger has a valid PCB.
This function can also be used to create a context for the threads
running on the CPUs that have been stopped when the debugger got
entered. This however is not done at the time of this commit.
/freebsd-10.2-release/sys/amd64/amd64/
H A Dmachdep.cdiff 131905 Sat Jul 10 19:56:00 MDT 2004 marcel Implement makectx(). The makectx() function is used by KDB to create
a PCB from a trapframe for purposes of unwinding the stack. The PCB
is used as the thread context and all but the thread that entered the
debugger has a valid PCB.
This function can also be used to create a context for the threads
running on the CPUs that have been stopped when the debugger got
entered. This however is not done at the time of this commit.

Completed in 786 milliseconds