reactos/drivers/base/nmidebug/nmidebug.rbuild

<?xml version="1.0"?>
<!DOCTYPE module SYSTEM "../../../tools/rbuild/project.dtd">
<module name="nmidebug" type="kernelmodedriver" installbase="system32/drivers" installname="nmidebug.sys">
	<bootstrap installbase="$(CDOUTPUT)" />
	<include base="null">.</include>
	<library>ntoskrnl</library>
	<library>hal</library>
	<file>nmidebug.c</file>
	<file>nmidebug.rc</file>
</module>
NMI Support Patch 13: [NMIDEBUG]: Add new NMI Debug driver. It registers an NMI callback on startup. The callback does nothing useful at the moment, but you can enhance it to add all sorts of debugging information that would otherwise be unavailable in situations such as an interrupt storm, IRQL hang, etc. When you send an NMI, such as by using QEMU, you should see the driver print a string. svn path=/trunk/; revision=44878 2010-01-02 04:50:08 +00:00			`<?xml version="1.0"?>`
			`<!DOCTYPE module SYSTEM "../../../tools/rbuild/project.dtd">`
			`<module name="nmidebug" type="kernelmodedriver" installbase="system32/drivers" installname="nmidebug.sys">`
[NTDLL]: Use LOCK instead of lock for SList assembly functions, this is a conditional such that on UP, "lock" instruction won't be generated. [NTDLL]: Apply the special begin/fault/resume lablels to the user-mode SList functions. Access faults can happen there due to a bug in the Windows algorithm, and Mm will need to handle that. [NTOS]: Lookup the special labels from above when initializing the System DLL. Only lookup INT2E vs SYSENTER on x86, other architectures don't need a stub. [NTOS]: Bitmap resources start at index 1, not 0. Also make sure we don't go past the maximum IDB_ resource index for no reason, and check the size of the resource instead of assuming it's going to be one page. [NMIDEBUG]: Fix and cleanup some code, and enable NMI support on the boot/install CD as well. svn path=/trunk/; revision=48860 2010-09-24 17:02:13 +00:00			`<bootstrap installbase="$(CDOUTPUT)" />`
NMI Support Patch 13: [NMIDEBUG]: Add new NMI Debug driver. It registers an NMI callback on startup. The callback does nothing useful at the moment, but you can enhance it to add all sorts of debugging information that would otherwise be unavailable in situations such as an interrupt storm, IRQL hang, etc. When you send an NMI, such as by using QEMU, you should see the driver print a string. svn path=/trunk/; revision=44878 2010-01-02 04:50:08 +00:00			`<include base="null">.</include>`
			`<library>ntoskrnl</library>`
			`<library>hal</library>`
			`<file>nmidebug.c</file>`
			`<file>nmidebug.rc</file>`
			`</module>`