[boost] bug in signals library? - segmentation fault (only linked) -> exit(11) called

From: Oliver.Kowalke_at_[hidden]
Date: 2005-12-23 04:36:24

Hello,
I get an segmentation fault if I try to link against
libboost_signals-gcc-1_33_1 or libboost_signals-gcc-mt-1_33_1!
The application consist only of an empty main function and the binary is
linked against the signals library.
I've appended an output (tusc.out) of tusc (trace unix system calls)
which indicates, that exit(11) is called and so a core dump created.

System: HP/UX 11.11 PA-RISC
Compiler: gcc-3.4.4 (with posix thread support)

Code:
int main( int argc, char* argv[])
{
        return 0;
}

Compiled with:
if g++ -DHAVE_CONFIG_H -I. -I/eda-home/kowalke/Projects/test/src -I..
-I/opt/boost/include/boost-1_33_1 -O0 -g3 -MT test.o -MD -MP -MF
".deps/test.Tpo" -c -o test.o
/eda-home/kowalke/Projects/test/src/test.cpp; then mv -f
".deps/test.Tpo" ".deps/test.Po"; else rm -f ".deps/test.Tpo"; exit 1;
fi
/bin/sh ../libtool --tag=CXX --mode=link g++ -O0 -g3 -o test
-L/opt/boost/lib test.o -lboost_signals-gcc-1_33_1 
mkdir .libs
g++ -O0 -g3 -o test test.o -L/opt/boost/lib -lboost_signals-gcc-1_33_1

 <<tusc.out>>