Anyone know of a good commercial debugger?
-
I was handed down a big windows base project at work that requires some attention. We have been experiencing some random crashes and bugs in the field. I’m working on debugging this issues but I need a little help. We have limited time to debug all issues so I was wondering if there are any commercially available tools (I’m currently looking at SOFTICE) that I could use to monitor the executable and record system parameters when the system is in the field. I need to pin point the root cause of the problems. I’m trying to get a sense of what’s going on in the field that’s causing the random behavior of the executable. Thank you
-
I was handed down a big windows base project at work that requires some attention. We have been experiencing some random crashes and bugs in the field. I’m working on debugging this issues but I need a little help. We have limited time to debug all issues so I was wondering if there are any commercially available tools (I’m currently looking at SOFTICE) that I could use to monitor the executable and record system parameters when the system is in the field. I need to pin point the root cause of the problems. I’m trying to get a sense of what’s going on in the field that’s causing the random behavior of the executable. Thank you
have you tried Visual Studio ? :rolleyes:
TOXCCT >>> GEII power
[VisualCalc 3.0 updated ][Flags Beginner's Guide new! ]
-
have you tried Visual Studio ? :rolleyes:
TOXCCT >>> GEII power
[VisualCalc 3.0 updated ][Flags Beginner's Guide new! ]
-
I was handed down a big windows base project at work that requires some attention. We have been experiencing some random crashes and bugs in the field. I’m working on debugging this issues but I need a little help. We have limited time to debug all issues so I was wondering if there are any commercially available tools (I’m currently looking at SOFTICE) that I could use to monitor the executable and record system parameters when the system is in the field. I need to pin point the root cause of the problems. I’m trying to get a sense of what’s going on in the field that’s causing the random behavior of the executable. Thank you
How is it that correlating the user dump file data with the PDB and source of your application is not sufficient to track this down? Is it memory corruption over time that is suspected? Then make a build that allows periodic memory validation to be performed and dump anything suspicious. Otherwise, a flat out crash can be diagnosed directly using the user dump file and the Microsoft Debugging Tools. What did you expect the 'good commecrial debugger' to do for you? People that start writing code immediately are programmers (or hackers), people that ask questions first are Software Engineers - Graham Shanks
-
I was handed down a big windows base project at work that requires some attention. We have been experiencing some random crashes and bugs in the field. I’m working on debugging this issues but I need a little help. We have limited time to debug all issues so I was wondering if there are any commercially available tools (I’m currently looking at SOFTICE) that I could use to monitor the executable and record system parameters when the system is in the field. I need to pin point the root cause of the problems. I’m trying to get a sense of what’s going on in the field that’s causing the random behavior of the executable. Thank you
I’m looking for more of a system level debugger. What I was told by a coworker is that there is software that works with you code to track bugs and system information (which was something that he read a long time ago). The "software" goes in the background of the source code and helps to log the parameters that lead up to the crash or the bug. I'm using visual studio when I run the code in debug mode, but I need to know what happens with the system in the field. I will be implementing debugging functionalities but it's going to take some time catch everything and I'm looking for a way to speed this up. Thank you for all the responses
-
I was handed down a big windows base project at work that requires some attention. We have been experiencing some random crashes and bugs in the field. I’m working on debugging this issues but I need a little help. We have limited time to debug all issues so I was wondering if there are any commercially available tools (I’m currently looking at SOFTICE) that I could use to monitor the executable and record system parameters when the system is in the field. I need to pin point the root cause of the problems. I’m trying to get a sense of what’s going on in the field that’s causing the random behavior of the executable. Thank you
The Visual Studio debugger is by far the best debugger for Windows development. There are entire books on a portion of the features it has. If you need something specific that the VS debugger doesn't do (or rather, doesn't give you all the information you would like), check out Compuware. They have some very powerful stuff to help debug a vast array of common issues (e.g. Bounds Checking). If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week Zac
-
I was handed down a big windows base project at work that requires some attention. We have been experiencing some random crashes and bugs in the field. I’m working on debugging this issues but I need a little help. We have limited time to debug all issues so I was wondering if there are any commercially available tools (I’m currently looking at SOFTICE) that I could use to monitor the executable and record system parameters when the system is in the field. I need to pin point the root cause of the problems. I’m trying to get a sense of what’s going on in the field that’s causing the random behavior of the executable. Thank you
I tried a very early demo version of a small part of this on my own PC several years ago. But it looks like the kind of thing you want. AppSight http://www.identify.com/products/win-net/index.php[^] Kevin
-
I tried a very early demo version of a small part of this on my own PC several years ago. But it looks like the kind of thing you want. AppSight http://www.identify.com/products/win-net/index.php[^] Kevin
I believe Numega Boundschecker does something similar. I used it once upon a time to find some memory leaks and it seemed to work ok, but that was about 7 years ago now. I think boundschecker's still around though in a new form. When I die I'd like to go peacefully in my sleep like my father, not screaming in terror like his passengers!!!
-
I believe Numega Boundschecker does something similar. I used it once upon a time to find some memory leaks and it seemed to work ok, but that was about 7 years ago now. I think boundschecker's still around though in a new form. When I die I'd like to go peacefully in my sleep like my father, not screaming in terror like his passengers!!!
As far as I can tell this AppSight stuff is quite different from Boundschecker. The idea is that you instrument an application out in the field - essentially provide it with a black box. Then the customer sends a file back to the developers. They open it in an IDE and you can step backwards and forwards through the code to see what's going on. It's geared towards the common scenario of "it works on the developers' machines but not the customers." Kevin