[Boost-bugs] [Boost C++ Libraries] #5185: Shared library libboost_graph_parallel calls exit() or _exit()

Subject: [Boost-bugs] [Boost C++ Libraries] #5185: Shared library libboost_graph_parallel calls exit() or _exit()
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2011-02-13 22:41:36

#5185: Shared library libboost_graph_parallel calls exit() or _exit()
--------------------------------------+-------------------------------------
 Reporter:  robert@…                  |       Owner:  asutton
     Type:  Bugs                      |      Status:  new    
Milestone:  To Be Determined          |   Component:  graph  
  Version:  Boost 1.46.0              |    Severity:  Problem
 Keywords:                            |  
--------------------------------------+-------------------------------------
 During a package review at Fedora
 (https://bugzilla.redhat.com/show_bug.cgi?id=673839) our rpmlint warned,
 that the shared library libboost_graph_parallel calls exit() or _exit():

 {{{
 boost-graph-mpich2.i686: W: shared-lib-calls-exit
 /usr/lib/mpich2/lib/libboost_graph_parallel.so.1.46.0 exit_at_GLIBC_2.0
 This library package calls exit() or _exit(), probably in a non-fork()
 context. Doing so from a library is strongly discouraged - when a library
 function calls exit(), it prevents the calling program from handling the
 error, reporting it to the user, closing files properly, and cleaning up
 any
 state that the program has. It is preferred for the library to return an
 actual error code and let the calling program decide how to handle the
 situation.

 boost-graph-mpich2.i686: W: shared-lib-calls-exit /usr/lib/mpich2/lib
 /libboost_graph_parallel-mt.so.1.46.0 exit_at_GLIBC_2.0
 This library package calls exit() or _exit(), probably in a non-fork()
 context. Doing so from a library is strongly discouraged - when a library
 function calls exit(), it prevents the calling program from handling the
 error, reporting it to the user, closing files properly, and cleaning up
 any
 state that the program has. It is preferred for the library to return an
 actual error code and let the calling program decide how to handle the
 situation.
 }}}

 May somebody more knowledged than me please investigate here, whether this
 exit()/_exit() is acceptable or whether it should be changed/rewritten
 (and if yes, do so)? Thank you very much.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/5185>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.