gEDA-bug: [Bug 698851] Re: libgeda calls exit()

["gpleda.org commit robot" <698851@xxxxxxxxxxxxxxxxxx>]

A commit was made which affects this bug
git master commit 0fc87a9d985e8bd4f98f77d5130e2515c286518c
http://git.gpleda.org/?p=gaf.git;a=commit;h=0fc87a9d985e8bd4f98f77d5130e2515c286518c

commit 0fc87a9d985e8bd4f98f77d5130e2515c286518c
Author: Peter TB Brett <peter@xxxxxxxxxxxxx>
Commit: Peter TB Brett <peter@xxxxxxxxxxxxx>

    libgeda: Remove some exit() calls and assertions.
    
    Try to avoid assertions in libgeda; instead, emit "critical"-level log
    messages and fail gently.  This patch removes a bunch of assertions
    and calls to exit() from libgeda, in favour of trying to keep going
    even in the face of programmer errors.
    
    Affects-bug: lp-698851

-- 
You received this bug notification because you are a member of gEDA Bug
Team, which is subscribed to gEDA.
https://bugs.launchpad.net/bugs/698851

Title:
  libgeda calls exit()

Status in GPL Electronic Design Automation tools:
  Fix Committed

Bug description:
  Hello,

    I am working on the Debian package for geda, when I ran lintian on
  the package, I got this:

   libgeda38: shlib-calls-exit usr/lib/libgeda.so.38.0.0                                                                                                      
                                                                                                                                                              
      The listed shared library calls the C library exit() or _exit()                                                                                         
      functions.                                                                                                                                              
                                                                                                                                                              
      In the case of an error, the library should instead return an                                                                                           
      appropriate error code to the calling program which can then determine                                                                                  
      how to handle the error, including performing any required clean-up.

  I am not sure if this is a real issue or not, since libgeda is most
  probably only used by the tools in geda. So I though of bringing this
  up here for you to decide.

To manage notifications about this bug go to:
https://bugs.launchpad.net/geda/+bug/698851/+subscriptions


_______________________________________________
geda-bug mailing list
geda-bug@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-bug