Re: Can't attach to process on CE device

Tech-Archive recommends: Fix windows errors by optimizing your registry



Are you using the standard SDK or a custom SDK? Toolhelp.dll is part
of the kernel debugger, so if your SDK wasn't built with the "Enable
Kernel Debugger" option checked, you'll probably have problems trying
to use it. (Even if you manually included the file.)

On my emulator toolhelp.dll is present in the \windows directory, and
it isn't read-only. When I try to attach to a running process with eVC
I get a message about not being able to find commdlg.dll, but I can
cancel past it.

BTW, attach to running process is a better way to debug in eVC. I
wrote a post about it a little while back.
("http://groups.google.com/group/microsoft.public.windowsce.embedded.vc/msg/f557199d4b5b7eff?dmode=source)

Hope part of my rambling helped,
Dan.

minorguy wrote:
> 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
    ... Although you may get the toolhelp DLL when you enable kernel debugger, ... attach to running process is a better way to debug in eVC. ... >> the target device. ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: Looking for toolhelp.lib for CE .NET 4.2
    ... The SDK ... of CE running on the target device. ... I develop an application with 'eMbedded Visual C++ 4.0 with Service pack ... I search web sites and 'toolhelp.lib' file is in the platform builder. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Compitible Problem
    ... You *must* install an SDK for a device which has ... You must get an SDK from the target device manufacturer. ... > the USB device, it regonizes my driver). ... I have tried to compile my program using all ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: VS2005 with CE 5.0 SDK
    ... I suppose that you could install the Windows Mobile 5 ... SDK, too, to see if that appears in the list. ... the target device is a CE 5.0 device. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Browsing for a folder on CE.NET 4.1
    ... Use the SDK for the actual target device. ... The Standard SDK is just a random assortment of OS components that Microsoft ... ever try to copy random libraries from some other SDK. ...
    (microsoft.public.windowsce.app.development)