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 without debug info but crashes when I'm debugging due to the low memory condition. (B.t.w. there is no out-of-memory exception, the allocation routines silently returns nil... is this something that can be fixed in FPC?) I tried with external debug info file but gdb goes crazy. (Stops at breakpoints but complete wrong ones). Also tried copying the .dbg file onto the wince device but it doesn't make a difference. Can wince be debugged with an external symbols file? Finally, how can I tell Lazarus to tell gdb to copy the compiled exe somewhere other than \gdb on the device? Thanks a lot for your help so far, Paul. On Thu, Apr 26, 2012 at 2:32 PM, Felipe Monteiro de Carvalho < felipemonteiro.carva...@gmail.com> wrote: > 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 Win32 API, so this won't help that much. > > Another debug solution is using DebugLn. > > Yet another one is using GDB tui interface from the command line. The > last time I used that was a long time ago, so I don't remember that > much anymore. In the forum there is a stiky post about that in the > WinCE section. > > -- > Felipe Monteiro de Carvalho > > -- > _______________________________________________ > Lazarus mailing list > Lazarus@lists.lazarus.freepascal.org > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus >
-- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus