'gwes.exe' errors

Daniel Moth

unread,

Jun 2, 2003, 7:12:51 AM6/2/03

to

CE 4.1/4.2 (retail build) device with released CF and HyperTerminal showing
OS debug messages (via serial port plugged to our device).

Hi

While running a CF application on CE 4.1 or 4.2 xscale board (250 or 255)
there are many debug messages like the following:

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.

Any ideas please?

Cheers
Daniel

mike

unread,

Jun 2, 2003, 8:50:25 AM6/2/03

to

Pretty sure this is expected behaviour for getting
exceptions into the debugger. check the release note? I've
seen it somewhere.

>.
>

Dave Bartlett

unread,

Jun 3, 2003, 5:10:21 AM6/3/03

to

Some of the software fallback routines that are provided
by the operating system and used by the display driver
have bugs on platforms that require aligned accesses.
These bugs are dependant on the blt type and the position
of the blt. The platforms you detail below has no
hardware accleration and hence will be using the software
fallback routines for most of the blts. I think Intel
have optimised some blt types in their display driver.

Run a debug build and examine the call stack to see
exactly were the problem is occurring.

DaveB

>.
>

Susan Loh [MS]

unread,

Jun 3, 2003, 1:21:57 PM6/3/03

to

Anytime you see a TLSKERN_NOFAULT message, it's because exceptions are
known to be a possible (accepted) occurrence at that time. For example as
I understand it, using invalid window handles will cause these messages to
be printed without breaking into the debugger. I'm the wrong person to
tell you if there's anything you could do to make them go away, but I do
know they're not serious.

Sue
sl...@microsoft.com (remove "online" from reply-to address)
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________________________________
Windows Embedded FAQ
(http://www.microsoft.com/windows/embedded/faq/default.asp)

--------------------
| From: "Daniel Moth" <dmo...@hotmail.com>
| Subject: 'gwes.exe' errors
| Date: Mon, 2 Jun 2003 12:12:51 +0100
| Lines: 28
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
| Message-ID: <#AGhfhPK...@TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.windowsce.platbuilder
| NNTP-Posting-Host: dsl-217-155-140-110.zen.co.uk 217.155.140.110
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.windowsce.platbuilder:33972
| X-Tomcat-NG: microsoft.public.windowsce.platbuilder

Daniel Moth

unread,

Jun 4, 2003, 7:19:20 AM6/4/03

to

Thank you...

There is nothing I can do to make them go away because they occur as part of
a call to the .NET Compact Framework libraries... Maybe someone from the
.NET CF team will be interested to look further into it...

Cheers
Daniel

""Susan Loh [MS]"" <sl...@online.microsoft.com> wrote in message
news:3VjVoSfK...@cpmsftngxa06.phx.gbl...