Tru64: Using stringstream to convert inbt/long to string causes application to crash

[avidamani]

Hi,

I have a c++ application compiled using

Compaq C++ V6.5-014 for Compaq Tru64 UNIX V5.1A (Rev. 1885)
Compiler Driver V6.5-014 (cxx) cxx Driver

The problem is that the application is having unaligned access error
and is core dumping whenever I use stringstream to convert integer or
long to string.

std::stringstre am x;
int y = 1234;
x << y;

But if I use the following code, i.e. initialize the stringstream
object using the constructor, i do not face the coree dump:

std::stringstre am x("");
int y = 1234;
x << y;

Can someone help me out in resolving theissue in the first code.

Thanks in advance.

- Avinash

[mlimber]

av*******@gmail .com wrote:

Hi,

I have a c++ application compiled using

Compaq C++ V6.5-014 for Compaq Tru64 UNIX V5.1A (Rev. 1885)
Compiler Driver V6.5-014 (cxx) cxx Driver

The problem is that the application is having unaligned access error
and is core dumping whenever I use stringstream to convert integer or
long to string.

std::stringstre am x;
int y = 1234;
x << y;

But if I use the following code, i.e. initialize the stringstream
object using the constructor, i do not face the coree dump:

std::stringstre am x("");
int y = 1234;
x << y;

Can someone help me out in resolving theissue in the first code.

Thanks in advance.

- Avinash

This sounds like a bug in your standard library implementation. Who is
your standard library vendor? Have you tried another implementation
(e.g., STL-port, Dinkumware, etc.)? What happens when you use
std::ostringstr eam with no initializer in the same way?

Cheers! --M

[avidamani]

>

This sounds like a bug in your standard library implementation. Who is
your standard library vendor?
How do I check that
Have you tried another implementation
(e.g., STL-port, Dinkumware, etc.)? What happens when you use
std::ostringstr eam with no initializer in the same way?

It still fails
Cheers! --M