FreeCADView Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000777 | FreeCAD | Bug | public | 2012-07-04 21:39 | 2012-07-05 11:25 |
| Reporter | hobbes1069 | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.12 | ||||
| Fixed in Version | 0.13 | ||||
| Summary | 0000777: Shared libraries call exit | ||||
| Description | While working on my package for Fedora I found the following issue: $ rpmlint rpmbuild/freecad/RPMS/x86_64/freecad-0.12-6.fc16.x86_64.rpm | grep shared-lib-calls-exit freecad.x86_64: W: shared-lib-calls-exit /usr/lib64/freecad/lib/libFreeCADGui.so exit@GLIBC_2.2.5 freecad.x86_64: W: shared-lib-calls-exit /usr/lib64/freecad/lib/libFreeCADApp.so exit@GLIBC_2.2.5 freecad.x86_64: W: shared-lib-calls-exit /usr/lib64/freecad/lib/libFreeCADBase.so exit@GLIBC_2.2.5 Explanation: $ rpmlint -I shared-lib-calls-exit shared-lib-calls-exit: 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. | ||||
| Tags | No tags attached. | ||||
| FreeCAD Information | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-07-04 21:39 | hobbes1069 | New Issue | |
| 2012-07-05 11:25 | wmayer | Note Added: 0002279 | |
| 2012-07-05 11:25 | wmayer | Status | new => closed |
| 2012-07-05 11:25 | wmayer | Resolution | open => fixed |
| 2012-07-05 11:25 | wmayer | Fixed in Version | => 0.13 |
