debugging on Pocket PC 2003

  • Thread starter Thread starter Detlef Grittner
  • Start date Start date
D

Detlef Grittner

I have installed VS.net 2003 and try to debug a simple C#
application. But every time I reach a breakpoint in the
code, the application on the PDA (an HP 5550 with Windows
Mobile 2003 and integrated .NET CF) crashes.
Visual Studio only shows a message, that the remote
connection to the PDA was interrupted.

Has anyone encountered this problem and knows how to solve
it?
 
Does it crash no matter where you put the breakpoint, or is the breakpoint
on a specific line of code every time?

Regards,
Christin Boyd

--------------------
| Content-Class: urn:content-classes:message
| From: "Detlef Grittner" <[email protected]>
| Sender: "Detlef Grittner" <[email protected]>
| Subject: debugging on Pocket PC 2003
| Date: Tue, 7 Oct 2003 15:10:13 -0700
| Lines: 9
| Message-ID: <[email protected]>
| 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: AcONH8fC5l8vIyH9QRah6WKShVdRIg==
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:35373
| NNTP-Posting-Host: TK2MSFTNGXA11 10.40.1.163
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
|
| I have installed VS.net 2003 and try to debug a simple C#
| application. But every time I reach a breakpoint in the
| code, the application on the PDA (an HP 5550 with Windows
| Mobile 2003 and integrated .NET CF) crashes.
| Visual Studio only shows a message, that the remote
| connection to the PDA was interrupted.
|
| Has anyone encountered this problem and knows how to solve
| it?
|
 
It crashes no matter where the breakpoint is.
-----Original Message-----
Does it crash no matter where you put the breakpoint, or is the breakpoint
on a specific line of code every time?

Regards,
Christin Boyd
....
 
Sounds like try blocks could be very helpful. If you haven't already wrapped
all your code in a try block... it is always a good practice. Try blocks
add no overhead to your application (until an exception occurs) and can be
invaluable in the debugging process. On an exception I usually pop-up a
message box that has the function name as the title and the exception
message in the body of the box.

Rick Winscot
www.zyche.com
 
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.
 
Try blocks
add no overhead to your application (until an exception occurs)

Irrelevant to the thread as a whole but for info a try..catch block prevents
inlining of the method (applicable in release build only of course)...

Cheers
Daniel
 
Detlef -

Is the debugger still crashing on you? I've talked to my testers and they
don't have a theory on why the debugger would crash when it reaches a
breakpoint on a real device. It does not seem like a timeout issue. Is it
possible that the debugger's buffer is getting filled up with too much
information and possibly resetting the connection? Does the disconnect
only happen in a certain point in code, and not in others? Waht is
different about that chunk of code? Lots of arrays, maybe recursive calls?


Regards,
Christin Boyd
Program Manager
Microsoft Corporation

This post is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "Detlef Grittner" <[email protected]>
| Sender: "Detlef Grittner" <[email protected]>
| References: <[email protected]>
<[email protected]>
<[email protected]>
<#[email protected]>
| Subject: Re: debugging on Pocket PC 2003
| Date: Fri, 7 Nov 2003 16:57:27 -0800
| Lines: 48
| Message-ID: <[email protected]>
| 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: AcOlk0eJ+HP2ANZrR46ii8VdDARZfg==
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:38079
| NNTP-Posting-Host: TK2MSFTNGXS01 10.40.2.125
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
|
| 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.
|
| >-----Original Message-----
| >Sounds like try blocks could be very helpful. If you
| haven't already wrapped
| >all your code in a try block... it is always a good
| practice. Try blocks
| >add no overhead to your application (until an exception
| occurs) and can be
| >invaluable in the debugging process. On an exception I
| usually pop-up a
| >message box that has the function name as the title and
| the exception
| >message in the body of the box.
| >
| >Rick Winscot
| >www.zyche.com
| >
| >
| >"Detlef Grittner" <[email protected]>
| wrote in message
| >| >> It crashes no matter where the breakpoint is.
| >>
| >> >-----Original Message-----
| >> >Does it crash no matter where you put the breakpoint,
| or
| >> is the breakpoint
| >> >on a specific line of code every time?
| >> >
| >> >Regards,
| >> >Christin Boyd
| >> >
| >> ...
| >
| >
| >.
| >
|
 
Is the debugger still crashing on you? I've talked to my testers and they
don't have a theory on why the debugger would crash when it reaches a
breakpoint on a real device. It does not seem like a timeout issue. Is it
possible that the debugger's buffer is getting filled up with too much
information and possibly resetting the connection? Does the disconnect
only happen in a certain point in code, and not in others? Waht is
different about that chunk of code? Lots of arrays, maybe recursive calls?

I too have this issue.
It has developed at some point as I used to havce no problems and
cannot think of any significant changes that I have made.
I have tried with a variety of devices and it occurs on some but not
on others.
See my other post on the subject for more details.


http://groups.google.com/[email protected]#link1
 
I'm going to follow up on this in the other thread titled "debugging on
Pocket PC 2003 - crashes on breakpoint" because that one has a little bit
more detail.

Regards,
Christin Boyd
Program Manager
Microsoft Corporation

This post is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Daniel Moth" <[email protected]>
| References: <[email protected]>
<[email protected]>
<[email protected]>
<#[email protected]>
| Subject: Re: debugging on Pocket PC 2003
| Date: Tue, 11 Nov 2003 11:55:19 -0000
| Lines: 41
| 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: dsl-217-155-140-110.zen.co.uk 217.155.140.110
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:38255
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
|
| >Try blocks
| > add no overhead to your application (until an exception occurs)
|
| Irrelevant to the thread as a whole but for info a try..catch block
prevents
| inlining of the method (applicable in release build only of course)...
|
| Cheers
| Daniel
|
|
| | > Sounds like try blocks could be very helpful. If you haven't already
| wrapped
| > all your code in a try block... it is always a good practice. Try
blocks
| > add no overhead to your application (until an exception occurs) and can
be
| > invaluable in the debugging process. On an exception I usually pop-up a
| > message box that has the function name as the title and the exception
| > message in the body of the box.
| >
| > Rick Winscot
| > www.zyche.com
| >
| >
| > | > > It crashes no matter where the breakpoint is.
| > >
| > > >-----Original Message-----
| > > >Does it crash no matter where you put the breakpoint, or
| > > is the breakpoint
| > > >on a specific line of code every time?
| > > >
| > > >Regards,
| > > >Christin Boyd
| > > >
| > > ...
| >
| >
|
|
|
 
Back
Top