public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Martin Kahlert <martin.kahlert@infineon.com>
To: gcc-gnats@gcc.gnu.org
Subject: c++/7012: istringstream cannot read integers on Solaris 2.5.1 / regression from 3.0.x
Date: Thu, 13 Jun 2002 02:46:00 -0000	[thread overview]
Message-ID: <200206130939.g5D9dDi28832@keksy.muc.infineon.com> (raw)


>Number:         7012
>Category:       c++
>Synopsis:       istringstream cannot read integers on Solaris 2.5.1
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 13 02:46:04 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Martin Kahlert
>Release:        3.1
>Organization:
Infineon AG
>Environment:
System: SunOS ultra 5.5.1 Generic_103640-37 sun4u sparc SUNW,Ultra-1
Architecture: sun4

	
host: sparc-sun-solaris2.5.1
build: sparc-sun-solaris2.5.1
target: sparc-sun-solaris2.5.1
configured with: ../gcc-3.1/configure --prefix=/home/software/GCC3.1 --exec-prefix=/home/software/GCC3.1/ULTRA --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --enable-languages=c++,f77 --disable-threads --enable-shared=libstdc++
>Description:
istringstream cannot read integers on Solaris 2.5.1
>How-To-Repeat:
$ cat t.cc
#include <iostream>
#include <sstream>

using namespace std;

int main(int argc,char *arv[])
{
 int i;
 istringstream offsets("1   4   0");

 offsets >> i;
 cout << i << endl;

 return 0;
}
$ g++ -o t t.cc
$ ./t
Segmentation fault

>Fix:
Do the same on Solaris 2.7 ;-) or use gcc-3.0.x
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-06-13  9:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200206130939.g5D9dDi28832@keksy.muc.infineon.com \
    --to=martin.kahlert@infineon.com \
    --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: 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).