public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: paolo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/10809: [3.3 regression] mips-sgi-irix6.5 libstdc++-v3 testsuite execution failure in 27_io/istream_unformatted.cc
Date: Mon, 19 May 2003 08:36:00 -0000	[thread overview]
Message-ID: <20030519083600.1933.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/10809; it has been noted by GNATS.

From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Paolo Carlini <pcarlini@unitus.it>
Cc: gcc-bugs@gcc.gnu.org,
 ghazi@caip.rutgers.edu,
 nobody@gcc.gnu.org,
 gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/10809: [3.3 regression] mips-sgi-irix6.5 libstdc++-v3 testsuite execution failure in 27_io/istream_unformatted.cc
Date: Mon, 19 May 2003 10:32:49 +0200

 > (*) Just copy the whole test file (together with the required
 > 'istream_unformatted-1.tst') and replace <testsuite_hooks.h> by
 > <cassert> and each VERIFY by assert. Then build and step into that
 > in_avail call.
 
 It's getting weirder: the log file contains
 
 Assertion failed: i != 0, file 
 /opt/build/eric/gcc-3_3-branch/src/libstdc++-v3/t
 estsuite/27_io/istream_unformatted.cc, line 606
 
 Now if I manually compile and run the test as you suggested, I get:
 
 Assertion failed: sum != 0, file istream_unformatted.cc, line 619
 
 and
 
 i = 4294967295 
 extracted = 0
 
 I get random bus errors with both GDB 5.2.1 and GDB 5.3. And I can't 
 step into in_avail (GDB jumps to the next line instead, after a little 
 delay), not too sure why.
 
 -- 
 Eric Botcazou


             reply	other threads:[~2003-05-19  8:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19  8:36 Eric Botcazou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-17 22:46 Paolo Carlini
2003-05-17 14:06 Eric Botcazou
2003-05-16 17:25 paolo
2003-05-16  7:36 Eric Botcazou
2003-05-16  1:46 ghazi

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=20030519083600.1933.qmail@sources.redhat.com \
    --to=ebotcazou@libertysurf.fr \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=paolo@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: link
Be 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).