archive
/
windows-server-2003
mirror of https://github.com/selfrender/Windows-Server-2003
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
4 Commits
1 Branch
0 Tags
1.5 GiB
 
 
 
 
 
 
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
windows-server-2003/ds/security/services/scerpc/ntsdexts
Shaswata Das 5c6fe3db62
Create README.md 		4 years ago
..
makefile commiting as it is 4 years ago
readme.txt commiting as it is 4 years ago
scedump.cpp commiting as it is 4 years ago
sceexts.cxx commiting as it is 4 years ago
sceexts.def commiting as it is 4 years ago
sceexts.h commiting as it is 4 years ago
sceexts.rc commiting as it is 4 years ago
sources commiting as it is 4 years ago

readme.txt 

Put sceExts.dll into the NT System32 directory.

Debugger extensions can be accessed by using either one of two methods:



1) Invoke ntsd normally, and refer to the dll name for

   each extension call.



    ntsd -p <processid for program>



    !sceExts.help

    !sceExts.DumpSceContext



(2) Invoke ntsd with the following:



    ntsd -a sceExts.dll -p<processid>



    Then extensions can simply be referenced by name.

     !help

     !DumpSceContext



    NOTE:  The argument order is important. I forget which way is correct.

    Either the -a or the -p must come first. It doesn't work the

    other way around.