[cfe-commits] r66078 - /cfe/trunk/Driver/clang.cpp

Mike Stump mrs at apple.com
Wed Mar 4 14:47:11 PST 2009

On Mar 4, 2009, at 1:41 PM, Chris Lattner wrote:
> Start making use of "pretty stack dumps" to get
> better crash info when clang crashes.  Step #2 of many.

I've noticed it is hard to search for a magic string to know when the  
compiler dies.  gcc does this by having the filename and line number  
stored someone and then calls into the error reporter with

   file.c:25: internal compiler error: ...

which make is easy to find the source line that might have caused the  
problem, leading to faster work arounds and potentially better bug  
reports.  The only thing I've noticed is '0     clang', which is too  
obscure and doesn't relate to the source.

Does this change improve that?

More information about the cfe-commits mailing list