"Valery Pryamikov"
<Valery.P...@nospam.sm.siemens.no> wrote in message
news:05bd01c31a23$bc33e140$a001...@phx.gbl...
> Hi,
> Anyone, please help me resolve my problem with debugging
> C# Winform Application on my Pocket PC. Debugger works
> without problems on emulator, but since emulator doesn't
> allow adding certificates to cert.stores - I can't debug
> my solution on emulator.
> When working with Pocket PC - applicaiton always
> successfully deployed without any problem. Starting
> application without debugging (Ctrl-F5) from IDE works
> as well, the only thing that doesn't work is DEBUGGING!
> I only get following error message in the output window:
> ---
> Build: 1 succeeded, 0 failed, 0 skipped
> Deploy: 1 succeeded, 0 failed, 0 skipped
>
>
> Launching Application
> Error while trying to run project: Unable to start
> debugging.
> ---
> I'm using:
> Microsoft Visual Studio.Net 2003 (final version)
> Enterprise Architect (English) version 7.1.3088.
>
> Microsoft Pocket PC version 3.0.11171 (build 11178)
> (English)
> .
>
> Fujitsu Siemens Pocket LOOX (60 MB).
>
> Thanks in advance,
> Regards,
> -Valery
I was able to get debugging working on my device (a CE 4.1 device) after
installing the Windows CE Utilities for VS 2003 Add-on Pack and changing the CPU
type to the one specified by the manufacturer. The Add-on Pack is here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=7ec99ca6-2095-4086-b0cc-7c6c39b28762&DisplayLang=en
However I don't believe that this should be necessary for a PocketPC device like
yours.
--
Ginny Caughey
Windows Embedded MVP
"Valery Pryamikov" <Valery.P...@nospam.sm.siemens.no> wrote in message
news:088701c31ac7$a5d35350$a501...@phx.gbl...
After further investigation it appears that problem is
somehow related to starting icordbg.dll in rundll32.exe.
Every single attempt to launch debugger session on device
populates tasks list with one more instance of
rundll32.exe that cosumes 60K and stays there until
computer shutdown. An attempt to attach windbg to this
rundll32.exe reports numerrous errors (always starting
with 0x8007012b). ProcessViewer from sysinternals reports
0xC0000142 error when I just try to click on such
rundll32.exe instance.
And during computer shutdown I get following event entry
in the system events log:
"Application popup: rundll32.exe - DLL Initialization
Failed : The application failed to initialize because the
window station is shutting down."
for each hanging rundll32.exe.
Regards,
-Valery.
Cheers,
Rich
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "Valery.Pryamikov" <Valery.P...@nospam.sm.siemens.no>
| Sender: "Valery.Pryamikov" <Valery.P...@nospam.sm.siemens.no>
| References: <088701c31ac7$a5d35350$a501...@phx.gbl>
<O$EM26tGD...@TK2MSFTNGP10.phx.gbl>
| Subject: Re: Unable to start debugging error (on device).
| Date: Thu, 15 May 2003 06:41:20 -0700
| Lines: 25
| Message-ID: <0c5101c31ae7$ab2bae40$a301...@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Thread-Index: AcMa56srMaw6FESHQPCC7BbRyoOwvA==
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:23277
| NNTP-Posting-Host: TK2MSFTNGXA11 10.40.1.163
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
BTW: I found really WEIRD way of making debugger working
on my computer and device:
At first I have to fail start debugger 3 times (so that
task manager shows 3 rundll32.exe 60K processes hanging
around). After that I hibernate computer; activate
computer again; disconnect and connect USB port to cardle
and viola - debugger is working now. Note that 3 fail
started debugger sessions seems to be important, since 2
or 4 didn't do it (think of not being superstitious after
that;-). Any other combination that I have tried (like
restarting computer/soft reset of device; disconnecting
and reconnecting device and other ways) didn't help.
That definitely points that some bug existing in
debugger's code that is triggered on my configuration...
Thanks and kind regards,
-Valery.
BTW: I found really WEIRD way of making debugger working
on my computer and device:
At first I have to fail start debugger 3 times (so that
task manager shows 3 rundll32.exe 60K processes hanging
around). After that I hibernate computer; activate
computer again; disconnect and connect USB port to cardle
and viola - debugger is working now. Note that the
sequence and 3 fail started debugger sessions seems to be
Rich
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "Valery Pryamikov" <Valery.P...@sm.siemens.no>
| Sender: "Valery Pryamikov" <Valery.P...@sm.siemens.no>
| References: <088701c31ac7$a5d35350$a501...@phx.gbl>
<O$EM26tGD...@TK2MSFTNGP10.phx.gbl>
<0c5101c31ae7$ab2bae40$a301...@phx.gbl>
<q5ISRs$GDHA...@cpmsftngxa06.phx.gbl>
| Subject: Re: Unable to start debugging error (on device).
| Date: Mon, 19 May 2003 00:15:09 -0700
| Lines: 47
| Message-ID: <01a701c31dd6$61d965b0$a001...@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcMd1mHZDcezWbw7S32LT6wAzpm2Yw==
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:23583
| NNTP-Posting-Host: TK2MSFTNGXA08 10.40.1.160
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
"Rich Hanbidge [MSFT]" <ric...@online.microsoft.com> wrote in message
news:YqSPFllH...@cpmsftngxa06.phx.gbl...
-Valery.
Can you try removing the wireless card, _soft_ reset the device, and
attempting to debug a simple application? You'll be running TCP over the
USB cable, which is a bit slower, but this will potentiall rule out the
wireless card.
Another option would be to borrow a device which works, and attempt to
debug on it from your machine. If you can debug against another device
with a similar configuration, I would think that implies your device is in
a bad state. Maybe try the converse on a neighbor's machine, attempt to
debug your device from their machine.
Are you building a custom CE image using PB? Do you have the latest
version of the NETCF? If you create a custom image with NETCF installed,
you will have a mis-match between the debugger and the device side bits,
which can cause problems.
That's all I can think of that could be causing you grief. Unfortunately,
these types of problems are hard to figure out without attaching a debugger.
Thanks for your patience!
Rich
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Alex Feinman [MVP]" <publi...@alexfeinman.com>
| References: <088701c31ac7$a5d35350$a501...@phx.gbl>
<O$EM26tGD...@TK2MSFTNGP10.phx.gbl>
<0c5101c31ae7$ab2bae40$a301...@phx.gbl>
<q5ISRs$GDHA...@cpmsftngxa06.phx.gbl>
<01a701c31dd6$61d965b0$a001...@phx.gbl>
<YqSPFllH...@cpmsftngxa06.phx.gbl>
| Subject: Re: Unable to start debugging error (on device).
| Date: Mon, 19 May 2003 16:27:30 -0700
| Lines: 91
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <OIcM54l...@TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| NNTP-Posting-Host: 204.249.181.133
| Path:
cpmsftngxa06.phx.gbl!cpmsftngxa07.phx.gbl!cpmsftngxa09.phx.gbl!TK2MSFTNGP08.
phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:23641
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework