2

I have a .net exe installed in the client machine and it throws an exception..So how to debug and find the exact error..

Please note that 1-this is not remote debugging.. 2-I dont have log files to check and the machine is Windows 7..

Please let me know if this is possible?

As per comments: As I already told I dont have log files to verify and I dont have any stackrace as well..

So anybody else know how to find the exact error..????

Dotnet
  • 299
  • 1
  • 4
  • 18
  • 1
    Assuming that the error only occurs on the client's computer, you are going to either need to put some logging into your executable so that you can have some visibility into what's going on, or install Visual Studio on the client's computer and perform your debugging there. – Robert Harvey Jul 25 '12 at 17:33
  • 1
    The exception thrown will have the error message and stack trace. Provided you don't swallow the exception, you should see this information which will be usefull to figure out what went wrong. By the way check this out http://stackoverflow.com/a/2299302/1221319 it might be helpful in your case – Esen Jul 25 '12 at 17:37

1 Answers1

1

Assuming the exe crashing (ie. the exception is unhandled) then if you are not able to install anything on the remote machine you will need to get a dump file from Windows Error Reporting.

For a managed executable you should configure WER to generate a full dump as the minidump will likely not have enough information.

Once you have this dump file on your machine you can analyze it using WinDbg and the SOS extension (assuming you have a matching pdb file for the exe that generated the dump file)

Rob Walker
  • 46,588
  • 15
  • 99
  • 136