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
| >> >
| >> ...
| >
| >
| >.
| >
|