Hi, exactly this examples/stream segfaults. Here is a stack-trace:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 182914822752 (LWP 19695)] 0x0000002a960af733 in std::operator<< <wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > () from /usr/lib64/libstdc++.so.5 (gdb) bt #0 0x0000002a960af733 in std::operator<< <wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > () from /usr/lib64/libstdc++.so.5 #1 0x0000000000402d88 in operator<< ([EMAIL PROTECTED], rhs=0x404796 "debug message ") at stream.h:139 #2 0x0000000000402f16 in main () at locationinfo.h:132 (gdb) I tried to figure ot, whats really happening, but I don't know. Tommi Am Donnerstag, 16. Dezember 2004 23:35 schrieb Curt Arnold: > There is a trivial example (examples/stream) that works for me. If you > are getting segfaults it is likely due to a problem in the core since I > haven't had a chance to work through the unit tests yet (which fail due > to a segfault). > > On Dec 16, 2004, at 2:56 PM, Tommi M�kitalo wrote: > > Hi, > > > > I just would like to know, if logstream works at all? The > > example-program > > segfaults, when it tries to print something. It is a platform-specific > > problem (SuSE 9.2/x86-84)? > > > > > > Tommi
