iostream????

[Ali]

Hi,

im using stl in a small testApp which linked against 2 libraries.

compiler: Compaq C++ V6.2-024 for Compaq Tru64 UNIX V5.1A (Rev. 1885)


flags: -g -gall -msg_quiet -using_std -D_ANSI_C_SOURCE....


ThHe problem is:
Whenever i use iostream in a cpp file in one of the librearies
i got this:

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,
recompilation 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 /shlib/libc.so (ladebug) up
2 0x3ff8013b530 in __cma_tis_mutex_lock(...) in /shlib/libc.so
3 0x3ff802e150c in __cxx_mutex_lock(...) in /shlib/libcxx.so
4 0x12003e624 in UnknownProcedure34FromFile273(...) in TestApp (ladebug) up
5 0x12003d930 in Init(...) in TestApp
6 0x3ffbffe1858 in __init_sti__cxxl_std_init_cpp_65f45f2a(...) in myLib.so
7 0x3ffbfffbbd8 in myLib.so
8 0x3ff800068e0

Any Idea??????????????/

Ali

 

[Ron Natalie]

Hi,

im using stl in a small testApp which linked against 2 libraries.

compiler: Compaq C++ V6.2-024 for Compaq Tru64 UNIX V5.1A (Rev. 1885)

You're best to ask in one of the alpha or Tru64 (fomerly called Digital Unix, formerly called
OSF/1) groups. This group doesn't address deficiencies of specific implementations.

 

[Ali]

Hi,

im using stl in a small testApp which linked against 2 libraries.

compiler: Compaq C++ V6.2-024 for Compaq Tru64 UNIX V5.1A (Rev. 1885)


flags: -g -gall -msg_quiet -using_std -D_ANSI_C_SOURCE....


ThHe problem is:
Whenever i use iostream in a cpp file in one of the librearies
i got this:
[snip]
Any Idea??????????????/

Ali

Hi Ali,

I've had the exact same problem and haven't found a solution to it
yet. There is definitely a problem when using iostream with certain
Tru64 libraries (in my case SS7). During startup, iostreams throws an
exception and then... boom. I've even duplicated this problem with
some simple test programs, but when I've rewritten them not to use
iostreams, then they've worked fine.

The only information I've found on HP's website is the following
information for the 6.5-0.31 version of the C++ compiler, in section
3.27 "Restrictions in Version 6.3":
http://h30097.www3.hp.com/cplus/rnu.htm

"A problem in libexc on Tru64 UNIX before Version 4.0E
generates an error message when an exception is thrown
from a constructor that will be called by a static
initialization, as in the following example. The error
message appears after the example. There is no workaround
for the problem."

I'm using the same version of the compiler as you, but am using an
earlier OS.
Compaq C++ V6.2-024 for Digital UNIX V4.0F (Rev. 1229)

I doubt any of this helps, but good luck just the same.
Dave

problem solved!
i have removed '__USR_STD_IOSTREAM' and it works fine. hmmmm

 

[David Cattarin]

problem solved!
i have removed '__USR_STD_IOSTREAM' and it works fine. hmmmm

You removed the symbol, or just stopped using iostreams?
Dave