[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#612341: shlib-calls-exit in lib*jpeg*'s



On Wed, 20 Mar 2013, DRC wrote:
> exit() is called by error_exit() in jerror.c, which is part of the
> libjpeg source.  error_exit() is part of the standard error manager
> for libjpeg.  Applications do not have to use that error manager.
> The TurboJPEG wrapper, specifically, uses its own custom error
> manager that will catch errors in the underlying libjpeg API and
> allow the TurboJPEG API functions to return an error code and set
> the TurboJPEG error string instead of exiting.

> The lintian warning is meant to clue you in to possible
> unintentional consequences of calling exit() within an API function,
> but this behavior in libjpeg is intentional and is not default (an
> application has to specifically request it.)  Thus, you can ignore
> the warning.

thank you for the details.  From this description it indeed sounds like
a good reason for a lintian override (probably in libjpeg8 as well)

-- 
Yaroslav O. Halchenko
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Senior Research Associate,     Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik        


Reply to: