Archived from groups: microsoft.public.pocketpc (More info?)
Hey
I want to debug some application on my pocket pc.
How I do that ?
I tried to copy the files to my computer and used the embedded
visual c++ 3.0 debug function but it gives me activesync server
connection error and to check if its running.
If i choose to use the emulator then it complains its not a ppc
application, also if i try to run it manually in the emulator using
the explorer same error.
Archived from groups: microsoft.public.pocketpc (More info?)
Did you write the application, or otherwise have access to the source code?
That is what is run in the eV Tools emulator.
--
Sven
MS-MVP Mobile Devices
"Roi" <blu@show.no-ip.org> wrote in message
newsan.2005.03.19.18.57.11.100039@show.no-ip.org...
> Hey
>
> I want to debug some application on my pocket pc.
> How I do that ?
>
> I tried to copy the files to my computer and used the embedded
> visual c++ 3.0 debug function but it gives me activesync server
> connection error and to check if its running.
>
> If i choose to use the emulator then it complains its not a ppc
> application, also if i try to run it manually in the emulator using
> the explorer same error.
>
>
> Can someone help me how to debug ppc apps ?
>
> thanks,
> Roi
>
Archived from groups: microsoft.public.pocketpc (More info?)
Roi wrote:
> Hey
>
> I want to debug some application on my pocket pc.
> How I do that ?
You need to set the target for compilation to the correct device for the
platform you are debugging on.
> I tried to copy the files to my computer and used the embedded
> visual c++ 3.0 debug function but it gives me activesync server
> connection error and to check if its running.
>
I'm not sure which files these are, executables, project files?
> If i choose to use the emulator then it complains its not a ppc
> application,
Because you haven't recompiled the application to run on the emualtor's
instruction set.
also if i try to run it manually in the emulator using
> the explorer same error.
Ditto.
Recompile your project but set your options to "Win32 Debug" and "POCKET
PC 2003 Emulator" to debug with the emulator, or "Win32 Debug" and
"POCKET PC 2003 Device" for PPC debugging.
Archived from groups: microsoft.public.pocketpc (More info?)
Roi wrote:
> On Sat, 19 Mar 2005 13:49:34 -0700, Sven wrote:
>
>
>>Did you write the application, or otherwise have access to the source code?
>>That is what is run in the eV Tools emulator.
>
>
> No I didnt.
Hmmm.
> I found out that only pocket pc 2003 sdk with evc 4 can emulate
> pocket pc apps.
The Windows CE Tools PPC emulator, for all intents and purposes, has an
x86 type processor. Therefore the application being debugged has to have
been compiled for the x86 instruction set.
> ..but still the error it gives me is for trying to use my real device
> instead of the emulator which should work anyway.
>
> any idea?
Archived from groups: microsoft.public.pocketpc (More info?)
RapiDbg which is included with the "Windows Mobile Developer Power Toys"
does what you want probably.
From the readme:
DESCRIPTION:
Tool displays currently running processes, modules loaded into process,
process/thread events and control inputs such as stylus taps and control
manipulation.
I've gotten process errors from other people's apps with it.
"Roi" <blu@show.no-ip.org> wrote in message
newsan.2005.03.19.18.57.11.100039@show.no-ip.org...
> Hey
>
> I want to debug some application on my pocket pc.
> How I do that ?
>
> I tried to copy the files to my computer and used the embedded
> visual c++ 3.0 debug function but it gives me activesync server
> connection error and to check if its running.
>
> If i choose to use the emulator then it complains its not a ppc
> application, also if i try to run it manually in the emulator using
> the explorer same error.
>
>
> Can someone help me how to debug ppc apps ?
>
> thanks,
> Roi
>
Archived from groups: microsoft.public.pocketpc (More info?)
You need to reassemble the module with all the debug options in order to
generate pseudo global labels that can be used to view variables and set
break-points in debug mode.
Alternatively, you could use a Disassembler to view the executable run
code - this will generate a pseudo Assembly-language with generic names for
labels and variables. Any modifications using this kind of technique on
other peoples' code is called reverse-engineering and is generally regarded
as being illegal and a breach of software copyrights.
"Roi" <blu@show.no-ip.org> wrote in message
newsan.2005.03.20.00.10.21.235760@show.no-ip.org...
> You sure ?
>
> I think i should be able to and it will show me assembly langauge
> like in normal debugging of normal windows applications
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.