debugging on Pocket PC 2003 - Crashes on breakpoint

  • Thread starter Thread starter Chris Auld
  • Start date Start date
C

Chris Auld

<snip>
The try catch blocks don't help in this case, because it's
the network connection that breaks down when the debugger
reaches a breakpoint during a debug session.
The release version of the program and even the debug
version (when not debugged in VS.net) run without
interruptions or exceptions.
That means the debugger crashes although my program has no
bug...
Does the debugger access some objects that are protected
by security?
I still don't know.
</snip>

Hi all... was this issue ever resolved? I am seeing the same symptoms
here... VS.Net 2k3, CF SP1, C#

Cheers
Chris
 
I'm seeing this problem on 2 of my machines and currently am at a loss as of
the reason. Suspect that this has to do with various SPs (1, 2) installed
and removed (?).
 
OK... lets get on top of this then ;-)

I can give a bit more detail, some attempted resolutions that have not
worked.

The issue is that when the debugger hits a break point when executing
against a remote device the connection is lost and the application on
the device exits without an error code. It occurs whether the ActiveSync
connection is established over USB, IRDA or WLAN.

I have a variety of Pocket PCs kicking around.....
Thus far I have tried it on my:
iPAQ 5400 - Issue Occurs
Panasonic Toughbook CF-P1 - Issue does not occur.

I have tried.
a) Hard resetting the iPAQ 5400
b) Uninstalling/Reinstalling activesync
c) Repairing my VS.NET install

I REALLY need this working again on the 5400 as I have some code
specific to that device to debug... I have a 5550 that is out with a
customer at the moment that I might be able to get back today....

Is anyone else seeing simlar issues?

Chris Auld
Kognition Consulting Limited
Strategy - Architecture - Implementation - Training
Microsoft Mobility Platform Specialists (e-mail address removed)
 
OK... more devices tested....
Everything works OK on my Symbol PDT8100

Chris Auld
Kognition Consulting Limited
Strategy - Architecture - Implementation - Training
Microsoft Mobility Platform Specialists (e-mail address removed)
 
Hi

I've experienced the loss of a debugging connection on an HP 5500 series
unit. It didn't necessarily happen ~on~ the break point and is not
guarenteed to always happen, but 'single stepping' is when it is likely
to happen if at all.


Paul
 
My experience is that only WM2003 devices are affected.
I've seen it with: Ipaq 36xx updated to 2003, XDA (PPCPE) and Toshiba e355
(native WM2003)
 
I've shown this thread to a couple of testers on my team. We're looking
around for an HP 5xxx device to test on. Our lab is full of newer Compaq
3600 and 3900 devices. I don't know if we ever tested on an HP 5550
device. I've sent mail to the other labs around Redmond to find a device
we can borrow.

I agree that it sounds like a problem with the connection between the
debugger on the desktop and the debugee on the device, rather than a bug in
the debugger itself.


Regards,
Christin Boyd
Program Manager
Microsoft Corporation

This post is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Alex Feinman [MVP]" <[email protected]>
| References: <[email protected]>
<[email protected]>
| Subject: Re: debugging on Pocket PC 2003 - Crashes on breakpoint
| Date: Thu, 11 Dec 2003 16:43:28 -0800
| Lines: 16
| 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: <#[email protected]>
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| NNTP-Posting-Host: 204.249.181.133
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.
phx.gbl
| Xref: cpmsftngxa07.phx.gbl
microsoft.public.dotnet.framework.compactframework:40694
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
|
| They will. Eventually.
|
| | > Anyone from MS care to comment?
| >
| > Chris Auld
| > Kognition Consulting Limited
| > Strategy - Architecture - Implementation - Training
| > Microsoft Mobility Platform Specialists (e-mail address removed)
| >
| >
| >
| > Don't just participate in USENET...get rewarded for it!
|
|
|
 
It seems to be a problem that develops over time though....
I have been sucessfully debugging on both a 5400 and 5550 for the past
couple of months and then one day it just decides to go 'tits up' on
me...
Thanks for looking into it though guys!

Cheers
Chris

P.S. Think I have an SP2 bug for ya too... will post on Monday.

Chris Auld
Kognition Consulting Limited
Strategy - Architecture - Implementation - Training
Microsoft Mobility Platform Specialists (e-mail address removed)
 
Why would you say that 3600 and 3900 are newer than h5xxx? I though it's
quite the opposite...
I can reproduce the problem on 3600 upgraded to 2003 at will - 100%. Same
thing with XDA1 upgraded to 2003. Let me know what kind of test you want me
to do...
 
Let's figure out what all of you on this thread have in common. It sounds
like you can reproduce it on devices which originally shipped as PPC 2002,
and then you flashed them to PPC 2003, is that correct? Or are some of you
experiencing this problem on devices that shipped as PPC 2003?

Are all of you using the same desktop OS?
Are all of you using the same NET CF Service Pack? 1 or 2?
Did all of you install the first drop of SP2 (which was buggy), then have
to uninstall, then reinstalled SP2 when it was released the second time?

Did all of you re-image your desktop machine between Everett Beta and the
RTM version of VS 2003?

My team did tons of testing by single stepping through code, but we can't
reproduce the problem. Let's narrow down the circumstances so that my lab
can run some automated tests. Thanks!

Regards,
Christin Boyd
Program Manager
Microsoft Corporation

This post is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Alex Feinman [MVP]" <[email protected]>
| References: <[email protected]>
<[email protected]>
<#[email protected]>
<[email protected]>
| Subject: Re: debugging on Pocket PC 2003 - Crashes on breakpoint
| Date: Sun, 21 Dec 2003 16:30:50 -0800
| Lines: 68
| 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: <[email protected]>
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| NNTP-Posting-Host: 204.249.181.133
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.
phx.gbl
| Xref: cpmsftngxa07.phx.gbl
microsoft.public.dotnet.framework.compactframework:41509
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
|
| Why would you say that 3600 and 3900 are newer than h5xxx? I though it's
| quite the opposite...
| I can reproduce the problem on 3600 upgraded to 2003 at will - 100%. Same
| thing with XDA1 upgraded to 2003. Let me know what kind of test you want
me
| to do...
|
| | > I've shown this thread to a couple of testers on my team. We're looking
| > around for an HP 5xxx device to test on. Our lab is full of newer
Compaq
| > 3600 and 3900 devices. I don't know if we ever tested on an HP 5550
| > device. I've sent mail to the other labs around Redmond to find a
device
| > we can borrow.
| >
| > I agree that it sounds like a problem with the connection between the
| > debugger on the desktop and the debugee on the device, rather than a bug
| in
| > the debugger itself.
| >
| >
| > Regards,
| > Christin Boyd
| > Program Manager
| > Microsoft Corporation
| >
| > This post is provided "AS IS" with no warranties, and confers no rights.
| > --------------------
| > | From: "Alex Feinman [MVP]" <[email protected]>
| > | References: <[email protected]>
| > <[email protected]>
| > | Subject: Re: debugging on Pocket PC 2003 - Crashes on breakpoint
| > | Date: Thu, 11 Dec 2003 16:43:28 -0800
| > | Lines: 16
| > | 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: <#[email protected]>
| > | Newsgroups: microsoft.public.dotnet.framework.compactframework
| > | NNTP-Posting-Host: 204.249.181.133
| > | Path:
| >
|
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.
| > phx.gbl
| > | Xref: cpmsftngxa07.phx.gbl
| > microsoft.public.dotnet.framework.compactframework:40694
| > | X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
| > |
| > | They will. Eventually.
| > |
| > | | > | > Anyone from MS care to comment?
| > | >
| > | > Chris Auld
| > | > Kognition Consulting Limited
| > | > Strategy - Architecture - Implementation - Training
| > | > Microsoft Mobility Platform Specialists (e-mail address removed)
| > | >
| > | >
| > | >
| > | > Don't just participate in USENET...get rewarded for it!
| > |
| > |
| > |
| >
|
|
|
 
Chris & Alex -

I talked to my developers and testers. They'd like to see the contents of
the output window after a crash. We have a theory that the debugger in the
device (mscoree.dll) is crashing. When you send the output window, please
tell us exactly which version of NET CF you're running. Thanks!

Regards,
Christin Boyd
Program Manager
Microsoft Corporation

This post is provided "AS IS" with no warranties, and confers no rights.
--------------------
| X-Tomcat-ID: 732304388
| References: <[email protected]>
<[email protected]>
<#[email protected]>
<[email protected]>
<[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: (e-mail address removed) (Christin Boyd [MS])
| Organization: Microsoft
| Date: Mon, 12 Jan 2004 23:55:43 GMT
| Subject: Re: debugging on Pocket PC 2003 - Crashes on breakpoint
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| Lines: 116
| Path: cpmsftngxa07.phx.gbl
| Xref: cpmsftngxa07.phx.gbl
microsoft.public.dotnet.framework.compactframework:42833
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Let's figure out what all of you on this thread have in common. It
sounds
| like you can reproduce it on devices which originally shipped as PPC
2002,
| and then you flashed them to PPC 2003, is that correct? Or are some of
you
| experiencing this problem on devices that shipped as PPC 2003?
|
| Are all of you using the same desktop OS?
| Are all of you using the same NET CF Service Pack? 1 or 2?
| Did all of you install the first drop of SP2 (which was buggy), then have
| to uninstall, then reinstalled SP2 when it was released the second time?
|
| Did all of you re-image your desktop machine between Everett Beta and the
| RTM version of VS 2003?
|
| My team did tons of testing by single stepping through code, but we can't
| reproduce the problem. Let's narrow down the circumstances so that my
lab
| can run some automated tests. Thanks!
|
| Regards,
| Christin Boyd
| Program Manager
| Microsoft Corporation
|
| This post is provided "AS IS" with no warranties, and confers no rights.
| --------------------
| | From: "Alex Feinman [MVP]" <[email protected]>
| | References: <[email protected]>
| <[email protected]>
| <#[email protected]>
| <[email protected]>
| | Subject: Re: debugging on Pocket PC 2003 - Crashes on breakpoint
| | Date: Sun, 21 Dec 2003 16:30:50 -0800
| | Lines: 68
| | 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: <[email protected]>
| | Newsgroups: microsoft.public.dotnet.framework.compactframework
| | NNTP-Posting-Host: 204.249.181.133
| | Path:
|
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.
| phx.gbl
| | Xref: cpmsftngxa07.phx.gbl
| microsoft.public.dotnet.framework.compactframework:41509
| | X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
| |
| | Why would you say that 3600 and 3900 are newer than h5xxx? I though it's
| | quite the opposite...
| | I can reproduce the problem on 3600 upgraded to 2003 at will - 100%.
Same
| | thing with XDA1 upgraded to 2003. Let me know what kind of test you
want
| me
| | to do...
| |
| | | | > I've shown this thread to a couple of testers on my team. We're
looking
| | > around for an HP 5xxx device to test on. Our lab is full of newer
| Compaq
| | > 3600 and 3900 devices. I don't know if we ever tested on an HP 5550
| | > device. I've sent mail to the other labs around Redmond to find a
| device
| | > we can borrow.
| | >
| | > I agree that it sounds like a problem with the connection between the
| | > debugger on the desktop and the debugee on the device, rather than a
bug
| | in
| | > the debugger itself.
| | >
| | >
| | > Regards,
| | > Christin Boyd
| | > Program Manager
| | > Microsoft Corporation
| | >
| | > This post is provided "AS IS" with no warranties, and confers no
rights.
| | > --------------------
| | > | From: "Alex Feinman [MVP]" <[email protected]>
| | > | References: <[email protected]>
| | > <[email protected]>
| | > | Subject: Re: debugging on Pocket PC 2003 - Crashes on breakpoint
| | > | Date: Thu, 11 Dec 2003 16:43:28 -0800
| | > | Lines: 16
| | > | 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: <#[email protected]>
| | > | Newsgroups: microsoft.public.dotnet.framework.compactframework
| | > | NNTP-Posting-Host: 204.249.181.133
| | > | Path:
| | >
| |
|
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.
| | > phx.gbl
| | > | Xref: cpmsftngxa07.phx.gbl
| | > microsoft.public.dotnet.framework.compactframework:40694
| | > | X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
| | > |
| | > | They will. Eventually.
| | > |
| | > | | | > | > Anyone from MS care to comment?
| | > | >
| | > | > Chris Auld
| | > | > Kognition Consulting Limited
| | > | > Strategy - Architecture - Implementation - Training
| | > | > Microsoft Mobility Platform Specialists (e-mail address removed)
| | > | >
| | > | >
| | > | >
| | > | > Don't just participate in USENET...get rewarded for it!
| | > |
| | > |
| | > |
| | >
| |
| |
| |
|
|
 
Your assumption seems to be correct. All devices I had this issue with are
upgraded former PPC 2002 devices with SA1100

I did not reimage my machines between beta and RTM

I'm seeing this on two XPSP1 machines and one W2K3 machine.

I am not seeing this on one of my machines that had the Everett beta
previously.

I am seeing this on three machines that had the Everett beta previously.

I had multiple builds of SP2 installed (beta, recalled, beta after recall
etc). The devices have been subjected to a hard reset in-between the SP
installs

This problem occurs on *any* breakpoint. There is no need to single-step
through the code. First breakpoint hit causes the error.

I can get you (or someone on your team) see the problem for yourself via
Remote Assistance session

Alex Feinman
 
Back
Top