[Lazarus] How do I debug wince LCL?

[Martin]

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 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?
>

Sorry this goes out of my area of knowledge. Couple of random things, 
that may or may not be helpful.
In environment options debugger, you can give gdb extra start up 
options. (But I wouldn't know of any that help)

Try dwarf vs stabs?

if you only need parts of the LCL, with debug info, maybe the following 
helps.
- Compile LCL with debug info.
- Remove *.ppu and *.o files for units that do not need dbg-info
- compile again without dbg info (so the missing files will be created)

Only the IDE is now to clever. It sees the changed options, and cleans 
the package.
Not sure if/where in the IDE to disable that. Otherwise do not change 
the settings in the IDE and call the compiler by hand (using 
--debug-log= you can get the exact fpc comand line issued by the IDE / 
take off any -g...).