On Fri, Aug 12, 2011 at 4:04 AM, Jan Safranek <jsafr...@redhat.com> wrote: > On 08/11/2011 08:25 PM, Dhaval Giani wrote: >> On Thu, Aug 11, 2011 at 9:02 AM, Jan Safranek <jsafr...@redhat.com> wrote: >>> The error macro should stop all processing, otherwise some NULL pointers >>> might >>> get dereferenced (e.g. lex.c:1323). >>> >> >> We do not want an exit sicne its part of the library. We want some >> non-fatal way out of processing. > > I had an impression that we call exit() somewhere else too, at least > rpmlint complains to me regularly, but I cannot find it now. I guess > rpmlint is wrong... >
I remember fixing it a while back. (that's also why I noticed this one ;-) ). > Anyway, any other suggestion? YY_FATAL_ERROR *must* stop other > processing, otherwise we get sigsegv, which is IMHO worse than exit(). > Unfortunately, I cannot think of something better right now. Propagate some error which will stop all sort of processing? Dhaval ------------------------------------------------------------------------------ FREE DOWNLOAD - uberSVN with Social Coding for Subversion. Subversion made easy with a complete admin console. Easy to use, easy to manage, easy to install, easy to extend. Get a Free download of the new open ALM Subversion platform now. http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Libcg-devel mailing list Libcg-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libcg-devel
