Can't attach to process on CE device

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I'm using eMbedded VC++ 4.0 with SP4. I'm trying to attach to a
process on the target device by selecting Build-->Start Debug-->Attach
to WCE Process. When I do this, I get a message box with the error
"Toolhelp.dll cannot be copied to the target device."


I am using Platform Builder 5.0 to build an image for my CEPC device,
the target device. I've included toolhelp.dll in the image. I've also
included the platform manager files needed for debugging over ethernet:
cemgrc.exe, tcpipc.dll and cetlkitl.dll. I use Platform Builder to
download the image to the CEPC. (I've worked around the problem of
cemgrc.exe exiting by writing a little app to ensure cemgrc.exe is
always running)

Then I go to eMbedded VC++ which is on a separate system. The program
I'm developing is a device driver. I can connect and download my DLL
to the target CE system OK over ethernet. I can use all the remote
tools OK, such as the process viewer and registry editor. But when I
select Attach to WCE Process, it tells me that "Toolhelp.dll cannot
be copied to the target device."

I've ensured that toolhelp.dll does exist on the target device. So I
don't know why eMbedded VC++ thinks it needs to download it. Although
the toolhelp.dll file is read-only on the target device---and it
won't seem to allow me to change that---I don't think that's the
problem. I got the same error even before I had built toolhelp.dll into
the CE image.

Any ideas on how I can fix this and attach to remote processes? I need
to attach to device.exe so I can debug my driver DLL as it gets loaded.

I did a search and only found one other person who had this same
problem and there were no replies. (
http://groups.google.com/group/microsoft.public.windowsce.embedded.vc/browse_frm/thread/13dcf7f410bdf2a4/005c6273f4b9d7b4?lnk=st&q=toolhelp.dll+cannot+be+copied+to+the+target+device&rnum=1#005c6273f4b9d7b4
)

Thanks.

.

Relevant Pages

  • Re: Cant attach to process on CE device
    ... Are you using the standard SDK or a custom SDK? ... Kernel Debugger" option checked, ... attach to running process is a better way to debug in eVC. ... > "Toolhelp.dll cannot be copied to the target device." ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: debug set up help
    ... the registry entry for the Platform Manager has the wrong path in it. ... > target device - a common occurance in a development environment. ... >> that you have enough free space in RAM to run the file viewer's CE piece, ... and room in the RAM filesystem to download it? ...
    (microsoft.public.windowsce.embedded.vc)
  • How to add Activesync func. in PB?
    ... Add Platform Manager->Base engine, ... However, when I try to connect host with the target device, it failed. ... And I had tried ActiveSync 3.1 and 3.7. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Error
    ... Studio is telling you it couldn't deploy the assembly to the target device. ... as the debugger can't attach to what's not ...
    (microsoft.public.pocketpc.developer)
  • flashing eboot makes the image downloading failed
    ... builder. ... If i attach the target device, it keeps on downloading and at one ...
    (microsoft.public.windowsce.platbuilder)