Many StormC users requested the possibility to have the breakpoints that were set in a previous debugging run reappear the next time that the debugger is started. Saved breakpoints are preserved even when the source text is modified. This can be an invaluable help for larger projects with many source files. Disassembler and CPU register display Assembly-language output is essential for full inspection of the program produced by the compiler. This window will let you set breakpoints at any location in memory.
Stack checking A so-called backtrace can also be tremendously useful for finding bugs.
This is made possible by the stack window's ability to document nested function calls. Profiler An absolute novelty is the newly-added code profiler. After developing a program, this tool is used to find the places in your code where most execution time is spent, and help you concentrate your optimization efforts on those places where they will do the most good. It does this by measuring the execution times of each function in the program while it is running. The product of this procedure is a table, which may be sorted by your own criteria, containing each function's name, the number of times it has been called, and the time spent in those calls.