Re: [ros-kernel] Problems with the last changes (mdl.c..)

[Hartmut B. <har...@te...>]

> -----Ursprungliche Nachricht-----
> Von:	we...@cw... [SMTP:we...@cw...]
> Gesendet am:	Montag, 20. Mai 2002 13:42
> An:	rea...@li...
> Betreff:	Re: [ros-kernel] Problems with the last changes (mdl.c..)
>
> I don't know. The crash report you posted shows the cr3 value as zero so
> most likely either the thread (or its parent process) being switched to
> is corrupt.

It seems, that cr3 is not printed correct. The faulting eip points to 'sti' 
within Ki386ContextSwitch. The correct value for cr3 is in eax. The 
faulting thread is created with PsCreateSystemThread from win32k. The 
context (cr3) is from win32k. The faulting address (cr2) points to the 
stack. It seems, that the stack is not visible for some processes. I've 
added a KeAttachProcess/KeDetacheProcess sequence in PsInitializeThread. 
This solves my problem.

- Hartmut

 ------ =_NextPart_000_01C2004A.FF5A19B0
Content-Type: application/octet-stream; name="create.c.diff"
Content-Transfer-Encoding: base64

DQpKOlxTYW5kYm94XFJvc1xyZWFjdG9zX3dvcmtcbnRvc2tybmxccHM+Y3ZzLmV4ZSAtZCA6ZXh0
OmhiaXJyQG1vay5sdmNtLmNvbTovQ1ZTL1JlYWN0T1MgLXo5IGRpZmYgLXUgY3JlYXRlLmMgICAg
ICAgDQpJbmRleDogY3JlYXRlLmMNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NClJDUyBmaWxlOiAvQ1ZTL1JlYWN0T1Mv
cmVhY3Rvcy9udG9za3JubC9wcy9jcmVhdGUuYyx2DQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuNDYN
CmRpZmYgLXUgLXIxLjQ2IGNyZWF0ZS5jDQotLS0gY3JlYXRlLmMJNSBNYXIgMjAwMiAwMDoyMDo1
NCAtMDAwMAkxLjQ2DQorKysgY3JlYXRlLmMJMjAgTWF5IDIwMDIgMjA6MDk6MTcgLTAwMDANCkBA
IC00MDAsOCArNDAwLDExIEBADQogICAgRFBSSU5UKCJUaHJlYWQgPSAleFxuIixUaHJlYWQpOw0K
ICAgIA0KICAgIFBpTnJUaHJlYWRzKys7DQotICAgDQorDQorICAgS2VBdHRhY2hQcm9jZXNzKFBy
b2Nlc3MpOw0KICAgIEtlSW5pdGlhbGl6ZVRocmVhZCgmUHJvY2Vzcy0+UGNiLCAmVGhyZWFkLT5U
Y2IsIEZpcnN0KTsNCisgICBLZURldGFjaFByb2Nlc3MoKTsNCisNCiAgICBUaHJlYWQtPlRocmVh
ZHNQcm9jZXNzID0gUHJvY2VzczsNCiAgICAvKg0KICAgICAqIEZJWE1FOiBXaGF0IGxvY2sgcHJv
dGVjdHMgdGhpcz8NCg==