mirror of
https://github.com/reactos/reactos.git
synced 2024-09-19 09:09:53 +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
15 lines
384 B
Ruby
15 lines
384 B
Ruby
3 stub InvokeOn32
|
|
4 stub IntOpInitialize
|
|
5 stub CallbackProcessing_3216
|
|
6 stub IUnknownObj32
|
|
8 stub CSm16ReleaseHandler_Release32
|
|
9 stub ThkMgrInitialize
|
|
10 stub ThkMgrUninitialize
|
|
11 stub TransformHRESULT_1632
|
|
12 stub TransformHRESULT_3216
|
|
13 stub ConvertObjDescriptor
|
|
14 stub ConvertHr1632Thunk
|
|
15 stub ConvertHr3216Thunk
|
|
16 stub IntOpUninitialize
|
|
18 stub ThkAddAppCompatFlag
|