stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Sebor <se...@roguewave.com>
Subject Re: Binary compatibility issue on solaris/gcc-4.1
Date Mon, 21 Apr 2008 18:42:01 GMT
Travis Vitek wrote:
> I believe that I have run into a binary compatibility issue on
> solaris/gcc-4.1.
> 
> A 12D build of 27.filebuf.codecvt works fine in 4.2.0, but if I use the
> 4.2.1 shared library I get 44418 failed assertions, and 1 fatal error
> which leads to an exit code of 9. I haven't had a chance to look into it
> yet, but I plan on doing so this afternoon.

I don't see this in my builds with gcc 3.4.2 on Red Hat EL 4 (in
12D build type) the test runs to completion with 0 assertion, but
I do see something similar in an HP aCC 6.16 build (12d). Here's
the output of the test from 4.2.0 when linked with 4.2.1:

$ ./27.filebuf.codecvt -q
# ASSERTION (S7) (4 lines):
# TEXT: rdstate () == eofbit | failbit, got goodbit
# CLAUSE: lib.filebuf
# LINE: 884

# ASSERTION (S7) (4 lines):
# TEXT: ifstream::read () extracted 30, expected 27
# CLAUSE: lib.filebuf
# LINE: 888

# ASSERTION (S7) (4 lines):
# TEXT: ifstream::read () got "abcdefghijklmnopqrstuvwxyz\x20", expected 
"abcdefghijklmnopqrstuvwxyz "
# CLAUSE: lib.filebuf
# LINE: 893

# ASSERTION (S7) (4 lines):
# TEXT: ifstream::read () extracted 30, expected 0
# CLAUSE: lib.filebuf
# LINE: 904

# +-----------------------+----------+----------+----------+
# | DIAGNOSTIC            |  ACTIVE  |   TOTAL  | INACTIVE |
# +-----------------------+----------+----------+----------+
# | (S1) INFO             |       45 |       45 |       0% |
# | (S7) ASSERTION        |        4 |    65838 |      99% |
# | (S9) FATAL            |        0 |      182 |     100% |
# +-----------------------+----------+----------+----------+


Mime
View raw message