mirror of
https://github.com/reactos/reactos.git
synced 2024-09-17 16:20:20 +00:00
e1ef078741
The idea then would be to have the following behaviour (when specifying the following options in the kernel command line): /DEBUGPORT=COMi --> load KDCOM.DLL and use COMi port (i == 1,2,3,4) if possible. /DEBUGPORT=FOO --> load KDFOO.DLL (useful for KDUSB.DLL, KD1394.DLL, KDBAZIS.DLL for VirtualKD, etc...) /DEBUGPORT=ROSDBG:[COMi|SCREEN|FILE|GDB|...] --> load KDROSDBG.DLL which contains the ROS kernel debugger, and use COMi or SCREEN or... as output port. svn path=/branches/kd++/; revision=58883
39 lines
1 KiB
ArmAsm
39 lines
1 KiB
ArmAsm
#include <internal/arm/asmmacro.S>
|
|
|
|
//
|
|
// Exceptions
|
|
//
|
|
GENERATE_ARM_STUB _abnormal_termination
|
|
GENERATE_ARM_STUB _except_handler2
|
|
GENERATE_ARM_STUB _except_handler3
|
|
GENERATE_ARM_STUB _global_unwind2
|
|
GENERATE_ARM_STUB _local_unwind2
|
|
GENERATE_ARM_STUB RtlGetCallersAddress
|
|
GENERATE_ARM_STUB RtlUnwind
|
|
GENERATE_ARM_STUB RtlDispatchException
|
|
GENERATE_ARM_STUB RtlpGetStackLimits
|
|
GENERATE_ARM_STUB DbgBreakPointWithStatus
|
|
GENERATE_ARM_STUB KeRaiseUserException
|
|
GENERATE_ARM_STUB KdpGdbStubInit
|
|
|
|
//
|
|
// Driver ISRs
|
|
//
|
|
GENERATE_ARM_STUB KeConnectInterrupt
|
|
GENERATE_ARM_STUB KeDisconnectInterrupt
|
|
GENERATE_ARM_STUB KiPassiveRelease
|
|
GENERATE_ARM_STUB KiInterruptTemplate
|
|
GENERATE_ARM_STUB KiUnexpectedInterrupt
|
|
GENERATE_ARM_STUB KeInitializeInterrupt
|
|
GENERATE_ARM_STUB KeSynchronizeExecution
|
|
|
|
//
|
|
// User Mode Support
|
|
//
|
|
GENERATE_ARM_STUB KeSwitchKernelStack
|
|
GENERATE_ARM_STUB RtlCreateUserThread
|
|
GENERATE_ARM_STUB RtlInitializeContext
|
|
GENERATE_ARM_STUB KeUserModeCallback
|
|
GENERATE_ARM_STUB KiCallUserMode
|
|
GENERATE_ARM_STUB NtCallbackReturn
|