What does TLSKERN_NOFAULT debug message mean?

I got the following message while debugging a problem on my system (4.1 on a
PXA255). What does it mean?

4294798479 PID:408a2512 TID:20680332 0x80671000: Data Abort: Thread=80671000
Proc=818f1ab0 'gwes.exe'
4294798481 PID:408a2512 TID:20680332 0x80671000: AKY=00000111 PC=0003f4b0
RA=0003f4ac BVA=0a000014 FSR=00000007
4294798482 PID:408a2512 TID:20680332 0x80671000: TLSKERN_NOFAULT set...
bypassing kernel debugger.
4294798484 PID:408a2512 TID:20680332 0x80671000: Calling exception handler
@0015cd58(0015d944) Frame=1204f170
4294798486 PID:408a2512 TID:20680332 0x80671000: exception dispostion = 4

Daniel
Thu Sep 04 10:31:06 CDT 2003

Sorry I don't know what they mean and would also like to find out...

I get them with our .NET CF app (CE 4.1 or 4.1 , PXA250 or 255 , CF with or
without SP1)...

e.g.
Data Abort: Thread=83bad400 Proc=80d9eb7c 'gwes.exe' AKY=00000089
PC=0003c720 RA=0003c718 BVA=0816cd50 FSR=00000007 TLSKERN_NOFAULT set...
bypassing kernel debugger.

PC, RA, BVA have different values dependent on what causes the message.

As far as I can narrow it down, the messages are output when using the
toolbar. In particular, adding toolbar buttons to the toolbar, changing the
ImageIndex, Style, Enabled, DropDownMenu of ToolBarButton, touching the
MinimiseBox, MaximiseBox, WindowStyle of Form and other areas.

Cheers
Daniel


"Danny" <danny.pacheco@teklogix.com> wrote in message
news:eCttnqVcDHA.3080@TK2MSFTNGP11.phx.gbl...
> I got the following message while debugging a problem on my system (4.1 on
a
> PXA255). What does it mean?
>
> 4294798479 PID:408a2512 TID:20680332 0x80671000: Data Abort:
Thread=80671000
> Proc=818f1ab0 'gwes.exe'
> 4294798481 PID:408a2512 TID:20680332 0x80671000: AKY=00000111 PC=0003f4b0
> RA=0003f4ac BVA=0a000014 FSR=00000007
> 4294798482 PID:408a2512 TID:20680332 0x80671000: TLSKERN_NOFAULT set...
> bypassing kernel debugger.
> 4294798484 PID:408a2512 TID:20680332 0x80671000: Calling exception handler
> @0015cd58(0015d944) Frame=1204f170
> 4294798486 PID:408a2512 TID:20680332 0x80671000: exception dispostion = 4
>
>
>

John
Thu Sep 04 12:01:26 CDT 2003

These messages are generated whenever there is an exception in the OS
(invalid pointer access/illegal instruction/etc...) and under normal
circumstances, you would break into a kernel debugger and the system would
stop... except that TLSKERN_NOFAULT was set, which causes the system to
continue operating and not break into the debugger.

Some apps do this when they are expecting an exception and have
__try/__except around it and breaking into the kernel debugger each time
would be annoying. I believe that gwes.exe will try to access the pointer
in a window handle structure to check its signature, wrapped in a
try/except, and if there is an invalid memory access gwes.exe simply returns
ERROR_INVALID_PARAMATER but continues operation. So likely you're seeing
this because you're passing an invalid handle around someplace.

--
John Spaith
Software Design Engineer, Windows CE
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2003 Microsoft Corporation. All rights
reserved.

"Danny" <danny.pacheco@teklogix.com> wrote in message
news:eCttnqVcDHA.3080@TK2MSFTNGP11.phx.gbl...
> I got the following message while debugging a problem on my system (4.1 on
a
> PXA255). What does it mean?
>
> 4294798479 PID:408a2512 TID:20680332 0x80671000: Data Abort:
Thread=80671000
> Proc=818f1ab0 'gwes.exe'
> 4294798481 PID:408a2512 TID:20680332 0x80671000: AKY=00000111 PC=0003f4b0
> RA=0003f4ac BVA=0a000014 FSR=00000007
> 4294798482 PID:408a2512 TID:20680332 0x80671000: TLSKERN_NOFAULT set...
> bypassing kernel debugger.
> 4294798484 PID:408a2512 TID:20680332 0x80671000: Calling exception handler
> @0015cd58(0015d944) Frame=1204f170
> 4294798486 PID:408a2512 TID:20680332 0x80671000: exception dispostion = 4
>
>
>