One nice way to debug it is compiling LCL-WinCE for the Win32
operating system. I made it work in desktop Windows to be able to
debug problems there. Unfortunatelly most of the remaining bugs do not
reproduce in desktop Windows and therefore are related to differences
between the WinCE API and
Thanks Martin Felipe,
C:\ in the search path solved my LCL problem.
I'm now running into memory trouble and hitting the 32MB process memory
limit. Without debug info my .exe is 5MB but it is 25MB with debug info and
it seems it is using up the same amounts of process memory. My app works
On 26/04/2012 15:30, Paul van Helden wrote:
Thanks Martin Felipe,
C:\ in the search path solved my LCL problem.
I'm now running into memory trouble and hitting the 32MB process
memory limit. Without debug info my .exe is 5MB but it is 25MB with
debug info and it seems it is using up the
Hi Martin,
Thanks, I deleted some breakpoints and placed new ones and the debugger now
works fine with external .dbg (not on device).
I also found this in the docs for changing the exe location:
--eval-command=set
remotedirectory \Storage Card\Program Files\My Program\bin and set the
Hi,
On 25/4/2012 9:46 μμ, Paul van Helden wrote:
I can step into LCL code when debugging a Win32 project, but a WINCE
project shows me the exact line number and file name in the stack
trace but always come up with Unable to load file
\lazarus\lcl\include\custombitmap.inc (for example). I've
Hi all,
I can step into LCL code when debugging a Win32 project, but a WINCE
project shows me the exact line number and file name in the stack trace but
always come up with Unable to load file
\lazarus\lcl\include\custombitmap.inc (for example). I've tried adding
search paths in debugger options
On 25/04/2012 19:46, Paul van Helden wrote:
Hi all,
I can step into LCL code when debugging a Win32 project, but a WINCE
project shows me the exact line number and file name in the stack
trace but always come up with Unable to load file
\lazarus\lcl\include\custombitmap.inc (for example).
