Bug #322
closedlibrary should not do exit() for error handling
0%
Description
It's impolite for a library to call exit().
We should find a better way to do error handling in those case
(
rom rpmlint:
libbabeltrace.x86_64: W: shared-lib-calls-exit /usr/lib64/libbabeltrace-ctf.so.0.0.0 exit@GLIBC_2.2.5
)
Its in the file:
babeltrace/formats/ctf/metadata/ctf-lexer.c
Updated by Yannick Brosseau over 11 years ago
From rpmlint:
libbabeltrace.x86_64: W: shared-lib-calls-exit /usr/lib64/libbabeltrace-ctf.so.0.0.0 exit@GLIBC_2.2.5
Its in the file:
babeltrace/formats/ctf/metadata/ctf-lexer.c
Updated by Mathieu Desnoyers over 11 years ago
- Status changed from New to Confirmed
The exit is generated by flex automatically. We can override it by providing our own yy_fatal_error implementation, but it won't allow us to do much better than a kill on self or something like that. Otherwise, we'd have to use setjmp/longjmp, but I'm not sure how portable they are.
Updated by Jonathan Rajotte Julien about 4 years ago
- Status changed from Confirmed to Invalid
State of babeltrace moved a lot since.
Closing this ticket as invalid. Reopen it if it stills apply to Babeltrace 2.