Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2010-03

Strange WinCE Bug

6 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Felipe Monteiro de Carvalho

Hello,

Who maintains the wince port and the arm port?

Some users are experiencing a very wierd bug in wince-arm which happens in pure lcl app or kol app + lnet (no idea what the common factor is). It also happens in some devices, but not all of them and acording to the reports it doesn't happen if you use FPC 2.2.0

Basically the app crashes if you turn the wireless on/off. It seams to me that the next instruction pointer gets corrupted in this call:

procedure TWinCEWidgetSet.AppProcessMessages;
var
  AMessage: TMsg;
  AccelTable: HACCEL;
  retVal, index: dword;
  pHandles: Windows.LPHANDLE;
begin
...
    retVal := Windows.MsgWaitForMultipleObjects(0,
      nil, False, 0, QS_ALLINPUT);

And goes somewhere random, even trying to call a variable in fpimage in some devices =D

What puzzles me is that this call is virtually impossible to have something wrong, so I guess it can only be either a compiler bug or a bug in Windows CE.

Normally I would create a bug report, but the bug is such that only some devices reproduce it and it's so obscure, so I'm afraid it's impossible to create a simple example that reproduces it. Here is the original thread:

http://www.lazarus.freepascal.org/index.php/topic,8498.0.html

What do you recommend? Simply creating a report?

thanks,

Felipe Monteiro de Carvalho

Reply by email

Felipe Monteiro de Carvalho
to Bernd Mueller
Bernd Mueller wrote
it looks, as if 2.4.x was not so well tested on Wince. Perhaps you could run the test suite and see if it is a compiler problem.

How can I do this?

Felipe Monteiro de Carvalho

Reply by email