#1
|
|||
|
|||
The Prepared environment for kernel programming
Hello,
Is there a custom Windows operating system for kernel programming? For example, the WDK package and the Visual Studio version related to it are installed And other settings for kernel programming and debugging It has been done Like This (Windows 10 Pro [1607] (x86/x64) Reverser Edition ISOs) : Code:
www.kernelmode.info/forum/viewtopic.php?f=22&t=4922&p=31664 |
#2
|
|||
|
|||
Enterprise grade Device Driver development is done with Standard OS images, debugging performed by running the driver in VirtualMachine (Kernel Development is rich of BSODs or worse scenarios with storage drivers that destroy Filesystem) and attaching in remote debug session with Windbg.
To setup the environment, you can use the following link: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/attaching-to-a-virtual-machine--kernel-mode- Best Regards, Evilcry |
The Following User Says Thank You to Evilcry For This Useful Post: | ||
tonyweb (06-18-2018) |
#3
|
|||
|
|||
Quote:
Isn't it going a bit too far ? I've got my content deleted there, and now you link it in the Recycle Bin ... |
#4
|
|||
|
|||
Perhaps maybe a trimmed version of a checked windows build?
hxxps://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/checked-build-of-windows |
#5
|
|||
|
|||
Quote:
For the development of complex (especially kernel-level) drivers, we use specialized trimmed builds of windows that are VERY lean. The logic being, that when we want to develop drivers and ensure that the driver(s) themselves are running and performing their functions without issues, it is a LOT easier to debug them when very few services are running in parallel on that system. Otherwise it becomes very tedious to debug at every stage and see as to whether the driver itself is faulty or whether compatibility with the running services is the issue. Also, the debugging itself is VERY fast with a system running a minimal set of services on it.It of course goes without saying that for kernel level debugging we require two machines (virtual or real). It is only when we have determined that the driver itself is functioning as expected, that we switch to debugging and testing on "real" systems that mimic the Retail Builds as closely as possible. Regards |
#6
|
|||
|
|||
I am sure if you have good connections with MSFT, you can get something like the Shared Source Initiative
Quote:
Otherwise Microsoft seems to encourage using the Checked Windows builds as per RiRye above. The question is in practice, what are the major companies out there doing? Last edited by chants; 06-28-2018 at 13:43. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Hades:Windows kernel driver lets reverse engineers monitor user and kernel mode code | sh3dow | Source Code | 0 | 05-12-2016 03:15 |
Armadillo Environment Variables Finder 1.2 | rukov | Community Tools | 3 | 12-16-2015 01:59 |
Armadillo Environment Variables & Visual Basic | D-Jester | General Discussion | 0 | 02-20-2005 10:27 |