SlickEdit Community

General => Community Forum => Topic started by: jjones on October 10, 2007, 01:20:26 pm

Title: New Blog Post: Using Binary Search to Debug Compiler Crashes
Post by: jjones on October 10, 2007, 01:20:26 pm
Using Binary Search to Debug Compiler Crashes
http://blog.slickedit.com/2007/10/using-binary-search-to-debug-compiler-crashes/

If you have used g++ and gcc over the years, you know that sometimes you get the worst compiler error of all:

Code: [Select]
g++: Internal error: Segmentation Fault (program cc1plus)

While this message is very friendly and informative, it doesn’t help you get your code compiled.

So, what do you do when your code masterpiece, for whatever reason, crashes the compiler. This typically happens, not when you are writing code, but when you update to a newer version of the compiler and amid your efforts to port your code base to the new compiler, the compiler dies.

Continue reading:  http://blog.slickedit.com/2007/10/using-binary-search-to-debug-compiler-crashes/