Hi,
How could I debug this error?
You can use the map files to find out where things went wrong. On the BSOD you attached you can find that the kernel crashed at <win32k.sys: 142f8>. So you can go to subsys/win32k/win32k.map and find (relative) address 142f8. If you compiled with DBG := 1 in your config file this should give you the exact source line where the crash occurred.
If you need a stack backtrace, use the values on the "Frames:" line in the same way.
Gé van Geldorp.
thank's for the hint Ge. The patch below should fix this issue. Who will apply this patch to cvs and has it the right format?
Theo
cvs -z9 diff desktop.c (in directory D:\home\willaxt\Entwicklung\ros\reactos\subsys\win32k\ntuser) Index: desktop.c =================================================================== RCS file: /CVS/ReactOS/reactos/subsys/win32k/ntuser/desktop.c,v retrieving revision 1.22 diff -r1.22 desktop.c 703c703 < *((DWORD*)Context) = *(DWORD*)ValueData; ---
*((DWORD*)EntryContext) = *(DWORD*)ValueData;
_________________________________________________________________ Die rote Karte für lästige E-Mails. MSN Hotmail mit Junk-Mail-Filter. http://www.msn.de/antispam/prevention/junkmailfilter Jetzt kostenlos anmelden!
Hi,
--- Theodor Willax theodor_willax@hotmail.com wrote:
thank's for the hint Ge. The patch below should fix this issue. Who will apply this patch to cvs and has it the right format?
It needs to be in diff -u format.
Thanks Steven
__________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com
From: Theodor Willax
Who will apply this patch to cvs
I just did, thanks for debugging and providing the patch
and has it the right format?
Not critical for a small patch like this, but it would be better if you could use "cvs diff -u" to get some context next time.
Gé van Geldorp.