public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> To: gcc-gnats@gcc.gnu.org Subject: libstdc++/6511: new libstdc++ v3 testsuite regressions on *-*-solaris2.8 Date: Mon, 29 Apr 2002 17:36:00 -0000 [thread overview] Message-ID: <200204300025.CAA23196@loge.TechFak.Uni-Bielefeld.DE> (raw) >Number: 6511 >Category: libstdc++ >Synopsis: new libstdc++ v3 testsuite regressions on *-*-solaris2.8 >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Apr 29 17:36:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Rainer Orth >Release: 3.1 20020426 (prerelease) >Organization: Faculty of Technology, Bielefeld University >Environment: System: SunOS loge 5.8 Generic_108528-10 sun4u sparc SUNW,Ultra-250 Architecture: sun4 host: sparc-sun-solaris2.8 build: sparc-sun-solaris2.8 target: sparc-sun-solaris2.8 same problem on System: SunOS arenal 5.8 Generic_111920-01 i86pc i386 i86pc Architecture: i86pc host: i386-pc-solaris2.8 build: i386-pc-solaris2.8 target: i386-pc-solaris2.8 configured with: /vol/gnu/src/gcc/gcc-3.1-branch-dist/configure --prefix=/vol/gcc --with-local-prefix=/vol/gcc --disable-nls >Description: Between 3.1 20020412 and 20020426, several libstdc++ testsuite failures started to occur on both Solaris 8/SPARC and Intel: +FAIL: 21_strings/inserters_extractors.cc execution test +FAIL: 24_iterators/istream_iterator.cc execution test +FAIL: 26_numerics/complex_inserters_extractors.cc execution test +FAIL: 27_io/instantiations.cc execution test +FAIL: 27_io/istream_extractor_char.cc execution test +FAIL: 27_io/istream_extractor_other.cc execution test +FAIL: 27_io/istream_manip.cc execution test +FAIL: 27_io/istream_seeks.cc execution test +FAIL: 27_io/istream_sentry.cc execution test +FAIL: 27_io/istream_unformatted.cc execution test +FAIL: 27_io/istringstream_members.cc execution test +FAIL: 27_io/ostream_inserter_arith.cc execution test +FAIL: 27_io/ostream_inserter_other.cc execution test +FAIL: 27_io/stringstream_members.cc execution test Those tests that existed in 3.0 passed there, so this is a regression. Running e.g. 24_iterators/istream_iterator.cc under gdb 5.2 (after compiling src/misc-inst.cc and test test proper with -g3 -gdwarf-2), I get the following stack trace: Program received signal SIGSEGV, Segmentation fault. 0x0002434c in sentry (this=0xffbef117, __in=@0xffbef488, __noskipws=82) at ctype_inline.h:40 40 { return _M_table[static_cast<unsigned char>(__c)] & __m; } (gdb) where #0 0x0002434c in sentry (this=0xffbef117, __in=@0xffbef488, __noskipws=82) at ctype_inline.h:40 #1 0x000244b4 in std::basic_istream<char, std::char_traits<char> >& std::operator>><char, std::char_traits<char> >(std::basic_istream<char, std::char_traits<char> >&, char&) (__in=@0xffbef118, __c=@0xffbef488) at istream.tcc:1021 #2 0x0001cd10 in std::istream_iterator<char, char, std::char_traits<char>, int>::_M_read() (this=0xffbef480) at stream_iterator.h:96 #3 0x0001caac in istream_iterator (this=0xffbef480, __s=@0xffbef488) at stream_iterator.h:60 #4 0x0001c4f4 in test02() () at /vol/gnu/src/gcc/gcc-3.1-branch-dist/libstdc++-v3/testsuite/24_iterators/istream_iterator.cc:65 #5 0x0001c9d8 in main () at /vol/gnu/src/gcc/gcc-3.1-branch-dist/libstdc++-v3/testsuite/24_iterators/istream_iterator.cc:89 >How-To-Repeat: Bootstrap and test on sparc-sun-solaris2.8. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-04-30 0:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-29 17:36 Rainer Orth [this message] 2002-04-30 2:14 bkoz 2002-04-30 2:17 bkoz 2002-04-30 8:26 Rainer Orth 2002-04-30 13:25 ro
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=200204300025.CAA23196@loge.TechFak.Uni-Bielefeld.DE \ --to=ro@techfak.uni-bielefeld.de \ --cc=gcc-gnats@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).