My company is experiencing a problem with a few of the programs it is writing and while many software engineers have tried to figure out what is going on they have had very little luck. I have been dragged in to this because I am a Network Engineer and for a while they suspected the network.
Anyway, the problem is this... Our software people have written a program in C that when run over the network on a Win2k machine hangs the entire machine. They can do this with the executable and/or while debugging the program. In the source they have paired down the commands to pretty much loading some variables and then a print statement and it still hangs. I suspect that it is the compiler linking in windows dlls but then I am not a programmer. One thing that makes debugging this program hard is that when it runs it takes only 2 seconds to hang the computer.
Since the software team is too busy to continue working on the problem they have left it up to me to figure out. I have gotten the software people to help me create a test machine that can reproduce the problem at will.
One thing I do know about this program is that it will only hang the computer when run as an ADMIN. With that knowledge I was hoping that there was a way that I could get Dr. Watson (or something else) running as an ADMIN to watch this program while it is run as a NON Admin. Then maybe I could see what it is trying to do. I was looking at WinDBG and noticed that you can remotely debug a program on another machine. Not sure how to use it yet.
Any suggestions???? Remember even though I have done some programming I am not a real programmer.