debug test-app on WinCE 6.0 with i486
lazarus / 12-Debugger

----------------------------------------------------------------------
pcler · 2014-01-28 05:54

Hallo

how can i debug my test-application on a Siemens panel with WinCe 6.0
and i486-cpu?
The Panel has a Ethernet-Port. I use Windows XP with Lazarus 1.0.8 and
FPC 2.6.2.

thanks

----------------------------------------------------------------------
Martin_fr · 2014-01-28 13:25

Isn't debugging on the emulator enough?

I haven't got any experience of my own with wince. But form the way
the debugger works, to debug on the device is remote debugging.
http://wiki.lazarus.freepascal.org/Remote_Debugging

Lazarus 1.2 supports two possibilities.

You either need a gdbserver, that can be installed and run on the
device.

Or you need a gdb.exe and an sshserver, that can both be installed and
run on the device. This 2nd method has however certain limitations.

That's it, there is no other way for the IDE to do remote debugging.

Alternatively, you can use any standalone debugger (that supports
debugging on the device)), and debug without the IDE. Such a debugger
needs to either know "stabs" or "dwarf"

----------------------------------------------------------------------
pcler · 2014-01-28 17:19

No sorry it's not enough.

My test-application works fine on the emulator (WinCE 5.0, i486),
but it doesn't work on the real device (WinCE 6.0, i486) and I have no
idea where the problem is.
I also can't find a emulator for WinCE 6.0.

So i must find a way for debugging on the device.
I will try your two examples.

Is the gdbserver for WinCE i486 part of Lazarus?

----------------------------------------------------------------------
Martin_fr · 2014-01-28 17:53

Lazarus does not ship any GDBserver at all.

As I said, I have no experience on the WinCe side myself.

I only know the debugger integration in Lazarus.

I do not know what GDb/gdbserver versions are available for wince. For
gdbserver you need Lazarus 1.2 (the RC will do)

But you need to find the gdb yourself (or hope someone else there has
the answer)

Google doesnt bring up much, so this may not be available.

-----
It may be easier to add logging to your app, and use a logfile (e.g.
lazlogger / debugln)

Or look for any other debugger that works on wince, and use it without
Lazarus. Though that may be hard to find since fpc encodes debug info
as either stabs or dwarf, but some windows debuggers expect yet a
different format.

----
Maybe compiling with -gl  (and no other debug info) will get an exe
small enough to fit on the device (if there is an issue). And then you
may be able to catch a stacktrace in a logfile (without using a
debugger).
But its just an idea, dont know if that will work.

----------------------------------------------------------------------
pcler · 2014-02-01 11:25

i find a link ( http://www.gnu.org/software/gdb/news/ )
they wrote

October 06, 2009: GDB 7.0 Released!
The latest version of GDB, version 7.0, is available for download.

Changes in this release include:

Support for native x86/x86_64 Darwin, x86_64 MinGW
Support for Lattice Mico32, x86/x86_64 DICOS, S+core 3 targets
gdbserver support for x86 Windows CE
Python scripting support
Reverse debugging, Process record and replay
Non-stop debugging
Multi-architecture debugging
Multi-inferior, multi-process debugging


I will download this gdbserver and run a test.
Then i give you a reply