Application Exits with no error

  • Thread starter Thread starter Simon
  • Start date Start date
S

Simon

Hey gang.

I'm trying to debug a seemingly random application crash we are being
reported about in the field.

Nobody has been able to reproduce with any consistent behaviour.

Almost every time we have discovered an obscure bug in our application there
is an exception like a DisposeException etc to go off of.

In this case the app just dissapears. It is a NETCF2sp2 application.

Any ideas what could cause a winforms app to suddenly just exit, and not
throw an exception or anything like that?

Is there any tools or anything I can do to figure out what is causing this?
It takes several hours of random testing for it to occur.

Our application is quite large so I have been looking at areas that could be
problematic but its a bit of a guessing game with such a large code base.

Any tools or ways to understand the stack trace before the app exits would
be superb ;)

Any help is much appreciated, thanks in advance!
 
Hi,
Take a look at the Remote Logging Configuration Tool from the .NET CF 3.5
Power Toys...
http://blogs.msdn.com/netcfteam/arc...compact-framework-3-5-have-been-released.aspx

You can watch how to use it here...
http://msdn.microsoft.com/en-us/netframework/cc647002.aspx

and here...
http://blogs.msdn.com/danhorbatt/archive/2007/11/01/remote-logging-wcf-on-net-compact-framework.aspx
(in your particular case, in step #2 you would check different options)


--

Alberto Silva
www.moving2u.pt - R&D Manager
http://msmvps.com/AlbertoSilva - Blog
Microsoft MVP - Device Application Development
 
Hi,
Take a look at the Remote Logging Configuration Tool from the .NET CF 3.5
Power Toys...http://blogs.msdn.com/netcfteam/archive/2007/12/13/power-toys-for-net...

You can watch how to use it here...http://msdn.microsoft.com/en-us/netframework/cc647002.aspx

and here...http://blogs.msdn.com/danhorbatt/archive/2007/11/01/remote-logging-wc...
(in your particular case, in step #2 you would check different options)
Click to expand...

Do you happen to be using Remote Data Access? I had an extremely hard
problem to figure out, finally Microsoft was able to find that there
was a hotfix for SQL 3.1 that fixed my problem.
 
Back
Top