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
31 lines
1 KiB
Ruby
31 lines
1 KiB
Ruby
@ stub -private DllRegisterServer
|
|
@ stub -private DllUnregisterServer
|
|
@ stub FreeCryptProvFromCert
|
|
@ stub GetCryptProvFromCert
|
|
@ stdcall PvkFreeCryptProv(ptr wstr long wstr)
|
|
@ stdcall PvkGetCryptProv(ptr wstr wstr long wstr wstr ptr ptr ptr)
|
|
@ stub PvkPrivateKeyAcquireContext
|
|
@ stub PvkPrivateKeyAcquireContextA
|
|
@ stdcall PvkPrivateKeyAcquireContextFromMemory(wstr long ptr long ptr wstr ptr ptr ptr)
|
|
@ stub PvkPrivateKeyAcquireContextFromMemoryA
|
|
@ stub PvkPrivateKeyLoad
|
|
@ stub PvkPrivateKeyLoadA
|
|
@ stub PvkPrivateKeyLoadFromMemory
|
|
@ stub PvkPrivateKeyLoadFromMemoryA
|
|
@ stub PvkPrivateKeyReleaseContext
|
|
@ stub PvkPrivateKeyReleaseContextA
|
|
@ stub PvkPrivateKeySave
|
|
@ stub PvkPrivateKeySaveA
|
|
@ stub PvkPrivateKeySaveToMemory
|
|
@ stub PvkPrivateKeySaveToMemoryA
|
|
@ stub SignError
|
|
@ stub SignerAddTimeStampResponse
|
|
@ stub SignerAddTimeStampResponseEx
|
|
@ stub SignerCreateTimeStampRequest
|
|
@ stub SignerFreeSignerContext
|
|
@ stub SignerSign
|
|
@ stub SignerSignEx
|
|
@ stub SignerTimeStamp
|
|
@ stub SignerTimeStampEx
|
|
@ stub SpcGetCertFromKey
|