Dll Debugging in eMb VC and PB.

I am attempting to debug a SOAP method using eMb VC. The debugger in eMb VC
is set to make the target's Internet Explorer the wrapper for the dll.
CEMON.exe and cemgrc.exe have been put in the the target's \windows\
directory. I have a breakpoint set in the C++ dll code in eMb VC. When in
eMb VC I go to "Build > Start Debug > Go" there is no visual indication in
eMb VC that it has stopped at that breakpoint. Instead Platform Builder
indicates it has stopped at a breakpoint in the function DebugBreak(). It
shows both assembly code and C++ code for this DebugBreak() function. This
function seems to be the standard function supplied in CE .NET for
breakpoints. I cannot step through C++ code in eMb VC. I can only step
through assembly code in Platform Builder. And there are so many steps of
assembly code to step through before getting to the method I want to debug
this setup is not practical for debugging.

Can I step through high level C++ dll code in eMb VC? If not is there a way
to make PB step through high level C++ code instead of assembly?

***
Remove the sj. from my email address if you wish to respond directly. It is
a spam jammer.

jamess
Mon Nov 29 19:28:43 CST 2004


The eVC debugger can source level debug DLL code as long as the DLL is
loaded by the process that you launched for debugging.
If you need to debug different processes at the same time, you should use
the PB debugger. To avoid assembly-only-debugging, you need to make sure
the PB debugger knows where the debug symbols are located to support source
level debugging. The PB debugger should prompt you asking where to find the
debug symbols if it doesn't find them on it's own at the load notification.

I do not recommend that you use both PB and eVC debugger at the same time.
It works but they do get in the way of each other.

Who is calling the DebugBreak() routine? It seems from your description,
some other process (one that you are not debugging with eVC) is calling
DebugBreak(). Again, you should be able to debug this with the PB debugger.

I hope this helps.

Regards,
James

Artist
Thu Dec 16 22:34:35 CST 2004

I am putting the DebugBreak() statements in because initially it is the only
way I can set a breakpoint. After it breaks on a DebugBreak() statement I
find I can set breakpoints elsewhere in the source files displayed by PB by
using the menu.

I have found that PB and eMb VC do get in the way of each other. Every time
I make a change in source code and recompile I have to download the entire
platform. I am trying to do debugging using eMb VC alone and so far have
been unsuccessful. Please see the thread "Remote Debugging Service dlls" I
started in microsoft.public.windowsce.embedded.

"James Stulz [MS]" <jamess@online.microsoft.com> wrote in message
news:9CDL1vn1EHA.768@cpmsftngxa10.phx.gbl...
>
> The eVC debugger can source level debug DLL code as long as the DLL is
> loaded by the process that you launched for debugging.
> If you need to debug different processes at the same time, you should use
> the PB debugger. To avoid assembly-only-debugging, you need to make sure
> the PB debugger knows where the debug symbols are located to support
> source
> level debugging. The PB debugger should prompt you asking where to find
> the
> debug symbols if it doesn't find them on it's own at the load
> notification.
>
> I do not recommend that you use both PB and eVC debugger at the same time.
> It works but they do get in the way of each other.
>
> Who is calling the DebugBreak() routine? It seems from your description,
> some other process (one that you are not debugging with eVC) is calling
> DebugBreak(). Again, you should be able to debug this with the PB
> debugger.
>
> I hope this helps.
>
> Regards,
> James
>