Bug #152
closedlibrary should not do exit() for error handling
100%
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
)
Updated by Mathieu Desnoyers about 12 years ago
- Status changed from New to Feedback
- Assignee set to Mathieu Desnoyers
should we use assertions instead ? At least those get turned off in distros.
Updated by Yannick Brosseau almost 12 years ago
- Status changed from Feedback to Confirmed
We recommand that we:
print on std error
assert
sigbus (or another appropriate signal)
With documenting that really really bad thing will trigger a signal.
Updated by Mathieu Desnoyers almost 12 years ago
- Status changed from Confirmed to Resolved
- % Done changed from 0 to 100
Applied in changeset 4a6d73787de534cbd7d5fc7a6b60af64de66e7ea.