C++Talk.NET C++ language newsgroups   Archives   FAQ   Search   Memberlist   Usergroups   Register   Profile   Log in to check your private messages   Log in  Re: coredump on true64          C++Talk.NET Forum Index -> C++ language (comp.lang.c++) View previous topic :: View next topic   Author Message Ali Guest Posted: Thu Jun 26, 2003 6:16 pm    Post subject: Re: coredump on true64 [email]ali_g_hamad (AT) hotmail (DOT) com[/email] (Ali) wrote in message news:<721ac515.0306250035.2883ec04 (AT) posting (DOT) google.com>... Quote: ali_g_hamad (AT) hotmail (DOT) com (Ali) wrote in message news:<721ac515.0306230850.5ec8f3b1 (AT) posting (DOT) google.com>... The problem occures when i just add some libraries without using them within the main routine and when i use the debug i get this msg: Thread received signal SEGV stopped at [<opaque> __pthread_mutex_lock(...) 0x3ff805686b0] "Gavin" <govin1 (AT) pacific (DOT) net.sg> wrote "Ali" <ali_g_hamad (AT) hotmail (DOT) com> wrote in message news:721ac515.0306200347.75a95459 (AT) posting (DOT) google.com... Hello, I am having this stl problem with unix tru64 compiler. -OSF1 V5.1 1885 alpha - Compaq C++ V6.2-024 for Compaq Tru64 UNIX V5.1A (Rev. 1885) run test result: exception system: exiting due to multiple internal errors: exception dispatch or unwind stuck in infinite loop exception dispatch or unwind stuck in infinite loop exception system: exiting due to multiple internal errors: exception dispatch or unwind stuck in infinite loop exception dispatch or unwind stuck in infinite loop Any help would be greatly appreciated. Thanks. Why don't you grep(search through) your coredump file, stack frame by stack frame, to see which exception caused for the memory to be dumped. Just a suggestion. Maybe you missed out on catching some exceptions, try using the the std::terminate( ) and set_unexpected function calls to catch and point out excatly where the exception was thrown. Gavin The problem has nothing to do with stl. because it occures when i use 2 libraries in my main routine if i merge the 2 libraries to oneit works fine. CXXFLAGS = -g -gall -msg_quiet -std ansi -nocurrent_include -distinguish_nested_enums -msg_disable narrowptr -pthread -D__USE_STD_IOSTREAM... This is the debug ouput: (ladebug) run Thread received signal SEGV stopped at [<opaque> __pthread_mutex_lock(...) 0x3ff805686b0] Information: An <opaque> type was presented during execution of the previous command. For complete type information on this symbol, recomp ilation of the program will be necessary. Consult the compiler man pages for details on producing full symbol table information using the ' -g' (and '-gall' for cxx) flags. (ladebug) up 1 0x3ff8013ac30 in __tis_mutex_lock(...) in /usr/shlib/libc.so (ladebug) up 2 0x3ff8013b530 in __cma_tis_mutex_lock(...) in /usr/shlib/libc.so (ladebug) up 3 0x3ff802e150c in __cxx_mutex_lock(...) in /usr/shlib/libcxx.so (ladebug) up 4 0x30001056c34 in UnknownProcedure34FromFile374(...) in myLib_1>.so (ladebug) up 5 0x30001055f40 in Init(...) in <myLib_1>.so (ladebug) up 6 0x3000183c0b8 in __init_sti__cxxl_std_init_cpp_65f45f2a(...) in myLib_2>.so (ladebug) up 7 0x30001869988 in /..../lib_d/<myLib_2>.so (ladebug) up 8 0x3ff800068e0 (ladebug) up 9 0x3ff8000f330 (ladebug) up 10 0x3ff8000f1f4 (ladebug) up 11 0x3ff8000f490 (ladebug) up 12 0x120013bcc in __start(...) in TestApp (ladebug) up Hi The reason seems to be clear now. i moved all overloaded operators from *.cpp to *.h files and it works. Does anybody knows a complier/linker option or somethingelse which might prevent that this error occures! Thanks alot Ali Back to top Ali Guest Posted: Sat Jul 05, 2003 11:10 am    Post subject: Re: coredump on true64 [email]ali_g_hamad (AT) hotmail (DOT) com[/email] (Ali) wrote in message news:<721ac515.0306261016.7f78f39 (AT) posting (DOT) google.com>... Quote: ali_g_hamad (AT) hotmail (DOT) com (Ali) wrote in message news:<721ac515.0306250035.2883ec04 (AT) posting (DOT) google.com>... [email]ali_g_hamad (AT) hotmail (DOT) com[/email] (Ali) wrote in message news:<721ac515.0306230850.5ec8f3b1 (AT) posting (DOT) google.com>... The problem occures when i just add some libraries without using them within the main routine and when i use the debug i get this msg: Thread received signal SEGV stopped at [<opaque> __pthread_mutex_lock(...) 0x3ff805686b0] "Gavin" <govin1 (AT) pacific (DOT) net.sg> wrote "Ali" <ali_g_hamad (AT) hotmail (DOT) com> wrote in message news:721ac515.0306200347.75a95459 (AT) posting (DOT) google.com... Hello, I am having this stl problem with unix tru64 compiler. -OSF1 V5.1 1885 alpha - Compaq C++ V6.2-024 for Compaq Tru64 UNIX V5.1A (Rev. 1885) run test result: exception system: exiting due to multiple internal errors: exception dispatch or unwind stuck in infinite loop exception dispatch or unwind stuck in infinite loop exception system: exiting due to multiple internal errors: exception dispatch or unwind stuck in infinite loop exception dispatch or unwind stuck in infinite loop Any help would be greatly appreciated. Thanks. Why don't you grep(search through) your coredump file, stack frame by stack frame, to see which exception caused for the memory to be dumped. Just a suggestion. Maybe you missed out on catching some exceptions, try using the the std::terminate( ) and set_unexpected function calls to catch and point out excatly where the exception was thrown. Gavin The problem has nothing to do with stl. because it occures when i use 2 libraries in my main routine if i merge the 2 libraries to oneit works fine. CXXFLAGS = -g -gall -msg_quiet -std ansi -nocurrent_include -distinguish_nested_enums -msg_disable narrowptr -pthread -D__USE_STD_IOSTREAM... This is the debug ouput: (ladebug) run Thread received signal SEGV stopped at [<opaque> __pthread_mutex_lock(...) 0x3ff805686b0] Information: An <opaque> type was presented during execution of the previous command. For complete type information on this symbol, recomp ilation of the program will be necessary. Consult the compiler man pages for details on producing full symbol table information using the ' -g' (and '-gall' for cxx) flags. (ladebug) up 1 0x3ff8013ac30 in __tis_mutex_lock(...) in /usr/shlib/libc.so (ladebug) up 2 0x3ff8013b530 in __cma_tis_mutex_lock(...) in /usr/shlib/libc.so (ladebug) up 3 0x3ff802e150c in __cxx_mutex_lock(...) in /usr/shlib/libcxx.so (ladebug) up 4 0x30001056c34 in UnknownProcedure34FromFile374(...) in myLib_1>.so (ladebug) up 5 0x30001055f40 in Init(...) in <myLib_1>.so (ladebug) up 6 0x3000183c0b8 in __init_sti__cxxl_std_init_cpp_65f45f2a(...) in myLib_2>.so (ladebug) up 7 0x30001869988 in /..../lib_d/<myLib_2>.so (ladebug) up 8 0x3ff800068e0 (ladebug) up 9 0x3ff8000f330 (ladebug) up 10 0x3ff8000f1f4 (ladebug) up 11 0x3ff8000f490 (ladebug) up 12 0x120013bcc in __start(...) in TestApp (ladebug) up Hi The reason seems to be clear now. i moved all overloaded operators from *.cpp to *.h files and it works. Does anybody knows a complier/linker option or somethingelse which might prevent that this error occures! Thanks alot Ali problem solved! i have removed '__USE_STD_IOSTREAM' Back to top Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First         C++Talk.NET Forum Index -> C++ language (comp.lang.c++) All times are GMT Page 1 of 1   Jump to: Select a forum C/C++----------------C LanguageC Language (Moderated)C++ Language (Moderated)C++ language (comp.lang.c++)C++ language, library and standards Non-English C/C++ Newsgroups----------------C++ (German)C++ (French)  You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum Powered by phpBB © 2001, 2006 phpBB Group SEO toolkit © 2004-2006 webmedic.