I am working on debugging this program which I have received from this Ph.D. Anyway, or after whatever the student finishes their thesis, now it is the responsibility of my debugging. The program basically moves to some text files and processes them. I am experiencing a problem (a segfault), because the program tries to use an array that has not been insatisfied so far. I was thinking that there is a debugging tool that lets you run through the program, and compares two different paths, which goes down the program. I think I can go through the program manually, but I would not like to do this because it is too big, and I still have not mastered it. I am using GDB and Valgrind (as well as G ++ -Wall used to show warnings), how I have received it so far but is there any software that you have described above, or Even through your program, you take only steps.
I think you are looking in the right direction with your choice of tools like GDB and Valgrind .
With GDB, you can see the execution of the program both script and call stack under the conditions when the default font is triggered. Then you can put a breakpop on that place and then run with such parameters, which do not crash the program and check the difference between the two.
Using Valgrind, which is actually a suite of tools (), you can callgrind and have some success in using kcachegrind. Callgrind lets you call graphs and cccgrind () So that you can imagine them. I used both of them to outline the performance of the big code base.
Another tool that can help you Fenris (), which can also print a call graph of your code. When reading your requirements, I think that the Fenreis is the closest because it allows you to The code path received is also allowed to 'visualize' the path.
No comments:
Post a Comment