Hi Darin, >>Is this for debug builds or for production builds? It is for production build.
>>If it is for debug builds, then adding file and line seems fine; we should do it in a way that shares code with assertion macros. So in-case of calling CRASH from ASSERT then it shouldn't print __FILE__ and __LINE__ right(because ASSERT prints all these)? >>If it is for production builds, then how do you debug other crashes? printf :( On 12 April 2013 20:17, Darin Adler <da...@apple.com> wrote: > Is this for debug builds or for production builds? > > If it is for debug builds, then adding file and line seems fine; we should > do it in a way that shares code with assertion macros. > > If it is for production builds, then how do you debug other crashes? > > -- Darin > -- *Arunprasad Rajkumar* http://in.linkedin.com/in/ararunprasad
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
