How to debug remote software installations

Thread View: comp.os.ms-windows.programmer.memory

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Jason Botwick Fri, 14 Jun 2002 11:40

#14

Author: Jason Botwick
Date: Fri, 14 Jun 2002 11:40

5 lines
1988 bytes

What's the best way to diagnose the cause of crashes that occur on software
that you have deployed to a user? When I was writing UNIX applications, we
could always examine the core dump. Is there some analogue under Windows?
Are there some tools that you can use to save the state of an application
when it crashes?

Re: How to debug remote software installations

#15

Author: josh
Date: Fri, 14 Jun 2002 15:03

24 lines
2602 bytes

On Fri, 14 Jun 2002 11:40:19 GMT, Jason Botwick 
<jbotwick@nc.rr.com> wrote:
> What's the best way to diagnose the cause of crashes that 
occur on software
> that you have deployed to a user? When I was writing UNIX 
applications, we
> could always examine the core dump. Is there some analogue 
under Windows?
> Are there some tools that you can use to save the state of an 
application
> when it crashes?
> 

Make sure they use Dr Watson (it's enabled by default on every 
Windows machine, but it can be disabled, so make sure it's 
*not* the case.) This thing generates a log and a core dump as 
well. Also, you can make your own app log stuff, so try that 
too. Finally, VC comes with a nifty little app, Remote 
Debugger, that you can use to actually debug their stuff over 
the net. 

There's also a great book on Windows debugging whose title I 
forget but something with "Debugging" in it, I think it's from 
Wrox, and it's very, very useful.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads