Project

General

Profile

Actions
Copy link

Bug #152

closed

library should not do exit() for error handling

Added by Yannick Brosseau about 12 years ago. Updated almost 12 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Mathieu Desnoyers
Target version:
-
Start date:
03/05/2012
Due date:
% Done:

100%

Estimated time:

Description

It's impolite for a library to call exit().

We should find a better way to do error handling in those case

(
See output of rpmlist ran on fedora:
liburcu.x86_64: W: shared-lib-calls-exit /usr/lib64/liburcu-qsbr.so.1.0.0 exit@GLIBC_2.2.5
liburcu.x86_64: W: shared-lib-calls-exit /usr/lib64/liburcu.so.1.0.0 exit@GLIBC_2.2.5
liburcu.x86_64: W: shared-lib-calls-exit /usr/lib64/liburcu-mb.so.1.0.0 exit@GLIBC_2.2.5
liburcu.x86_64: W: shared-lib-calls-exit /usr/lib64/liburcu-bp.so.1.0.0 exit@GLIBC_2.2.5
liburcu.x86_64: W: shared-lib-calls-exit /usr/lib64/liburcu-signal.so.1.0.0 exit@GLIBC_2.2.5
)

Related issues 1 (0 open — 1 closed)

Related to LTTng-UST - Bug #267: library should not do exit() for error handlingWon't fixMathieu Desnoyers03/05/2012

Actions
Actions
Copy link

Also available in: Atom PDF