Re: libstdc++/8655: Problematic behaviour of std::ends

Re: libstdc++/8655: Problematic behaviour of std::ends

[Ioannis Papadopoulos]

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

From: Ioannis Papadopoulos <Ioannis.Papadopoulos@cern.ch>
To: reichelt@igpm.rwth-aachen.de, <Ioannis.Papadopoulos@cern.ch>,
   <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <nobody@gcc.gnu.org>,
   <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: libstdc++/8655: Problematic behaviour of std::ends
Date: Wed, 20 Nov 2002 17:05:16 +0100 (CET)

 Hello,
 
 this problems appears on:
 
 1) Redhat Linux 7.2 and 7.3
 Output of gcc -v:
 
 Reading specs from 
 /usr/local/gcc-alt-3.2/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
 Configured with: ./configure --prefix=/usr/local/gcc-alt-3.2 --enable-shared
 Thread model: posix
 gcc version 3.2
 
 2) SuSE Linuz 8.0
 Output of gcc -v:
   
 Reading specs from 
 /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
 Configured with: /root/gcc-3.2/configure 
 Thread model: posix
 gcc version 3.2
 
 >     Are you really sure, you don't get the null charachter?
 >     Nedit displays it as "<soh>" and emacs as "^@".
 
 This is exactly what I get, and this is my problem!
 Moreover the C-string is always terminated at the first such character, as 
 the output of the example code shows:
 
 String size = 6
 C-string size = 5
 i = 1
 i = 1
 2nd string size = 9
 2nd C-string size = 5
 i = 1_1
 i = 1
 
 This behaviour did not exist on earlier versions of gcc, eg. 2.95.x
 
 Kind regards,
 Ioannis.
 
 
 On 20 Nov 2002 reichelt@igpm.rwth-aachen.de wrote:
 
 > Synopsis: Problematic behaviour of std::ends
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: reichelt
 > State-Changed-When: Wed Nov 20 05:57:08 2002
 > State-Changed-Why:
 >     I can't reproduce your problem with gcc 3.2 on i686-pc-linux-gnu.
 >     However, you did not specify the exact system configuration
 >     (output of gcc -v) and whether any optimization was used or
 >     not.
 >     
 >     Are you really sure, you don't get the null charachter?
 >     Nedit displays it as "<soh>" and emacs as "^@".
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8655
 > 
 
 -- 
 _____________________________________________________________________
 Ioannis PAPADOPOULOS  European Laboratory for Particle Physics (CERN)
                       IT Division, Geneva 23, CH-1211 Switzerland
                       office: 513-R-042, mailbox: G09100
                       tel:(+41 22 76) 74672, fax:(+41 22 76) 76830              
                       e-mail: Ioannis.Papadopoulos@cern.ch
                       URL: http://cern.ch/Ioannis.Papadopoulos
 

Re: libstdc++/8655: Problematic behaviour of std::ends

[paolo]

Synopsis: Problematic behaviour of std::ends

State-Changed-From-To: feedback->closed
State-Changed-By: paolo
State-Changed-When: Wed Nov 20 12:08:46 2002
State-Changed-Why:
    As Wolfgang says, not a bug, duplicate of libstdc++/5737.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8655

Re: libstdc++/8655: Problematic behaviour of std::ends

[Wolfgang Bangerth]

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>,
   Ioannis Papadopoulos <Ioannis.Papadopoulos@cern.ch>
Cc:  
Subject: Re: libstdc++/8655: Problematic behaviour of std::ends
Date: Wed, 20 Nov 2002 10:49:08 -0600 (CST)

 Ioannis,
 
 This problem is exactly what PR 5735 was about. I found that equally 
 annoying, but apparently gcc2.95 was not standards conforming, and gcc3 
 is. I work around this by only appending the std::ends when using gcc2.95, 
 using the preprocessor for this. Unfortunately, gcc2.95 needs this since 
 otherwise it will return a non-terminated string, which is of course 
 useless when assigned to a char*. This is one of the more annoying 
 incompatibilities between 2.95 and 3.x :-(
 
 Read the audit trail of this report.
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 
 

Re: libstdc++/8655: Problematic behaviour of std::ends

[reichelt]

Synopsis: Problematic behaviour of std::ends

State-Changed-From-To: open->feedback
State-Changed-By: reichelt
State-Changed-When: Wed Nov 20 05:57:08 2002
State-Changed-Why:
    I can't reproduce your problem with gcc 3.2 on i686-pc-linux-gnu.
    However, you did not specify the exact system configuration
    (output of gcc -v) and whether any optimization was used or
    not.
    
    Are you really sure, you don't get the null charachter?
    Nedit displays it as "<soh>" and emacs as "^@".

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8655

Re: libstdc++/8655: Problematic behaviour of std::ends

[paolo]

Synopsis: Problematic behaviour of std::ends

State-Changed-From-To: feedback->open
State-Changed-By: paolo
State-Changed-When: Wed Nov 20 05:07:28 2002
State-Changed-Why:
    Attachment received.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8655

Re: libstdc++/8655: Problematic behaviour of std::ends

[Ioannis Papadopoulos]

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

From: Ioannis Papadopoulos <Ioannis.Papadopoulos@cern.ch>
To: paolo@gcc.gnu.org, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
   <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: libstdc++/8655: Problematic behaviour of std::ends
Date: Wed, 20 Nov 2002 14:01:25 +0100 (CET)

   This message is in MIME format.  The first part should be readable text,
   while the remaining parts are likely unreadable without MIME-aware tools.
   Send mail to mime@docserver.cac.washington.edu for more info.
 
 ---1970702844-1785715624-1037797285=:23333
 Content-Type: TEXT/PLAIN; charset=US-ASCII
 
 Hello,
 
 I send you the attachment which got lost.
 
 Kind regards,
 Ioannis.
 
 On 20 Nov 2002 paolo@gcc.gnu.org wrote:
 
 > Synopsis: Problematic behaviour of std::ends
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: paolo
 > State-Changed-When: Wed Nov 20 04:50:29 2002
 > State-Changed-Why:
 >     Unfortunately, the attachment got lost. Could you possibly
 >     provide it again?
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8655
 > 
 
 -- 
 _____________________________________________________________________
 Ioannis PAPADOPOULOS  European Laboratory for Particle Physics (CERN)
                       IT Division, Geneva 23, CH-1211 Switzerland
                       office: 513-R-042, mailbox: G09100
                       tel:(+41 22 76) 74672, fax:(+41 22 76) 76830              
                       e-mail: Ioannis.Papadopoulos@cern.ch
                       URL: http://cern.ch/Ioannis.Papadopoulos
 
 ---1970702844-1785715624-1037797285=:23333
 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="sl.cpp"
 Content-Transfer-Encoding: BASE64
 Content-ID: <Pine.LNX.4.44.0211201401250.23333@lxplus071.cern.ch>
 Content-Description: 
 Content-Disposition: attachment; filename="sl.cpp"
 
 I2luY2x1ZGUgPGlvc3RyZWFtPg0KI2luY2x1ZGUgPHN0cmluZz4NCg0KI2lu
 Y2x1ZGUgPHNzdHJlYW0+DQoNCmludCBtYWluKCBpbnQsIGNoYXIqKikNCnsN
 CiAgc3RkOjpvc3RyaW5nc3RyZWFtIG9zOw0KICBpbnQgaSA9IDE7DQogIG9z
 IDw8ICJpID0gIiA8PCBpIDw8IHN0ZDo6ZW5kczsNCiAgY29uc3Qgc3RkOjpz
 dHJpbmcgcyA9IG9zLnN0cigpOw0KICBzdGQ6OmNvdXQgPDwgIlN0cmluZyBz
 aXplID0gIiA8PCBzLnNpemUoKSA8PCBzdGQ6OmVuZGw7DQogIGNvbnN0IGNo
 YXIqIHNjID0gcy5jX3N0cigpOw0KICBzdGQ6OmNvdXQgPDwgIkMtc3RyaW5n
 IHNpemUgPSAiIDw8IHN0ZDo6c3RybGVuKCBzYyApIDw8IHN0ZDo6ZW5kbDsN
 CiAgc3RkOjpjb3V0IDw8IHMgPDwgc3RkOjplbmRsOw0KICBzdGQ6OmNvdXQg
 PDwgc2MgPDwgc3RkOjplbmRsOw0KDQogIHN0ZDo6b3N0cmluZ3N0cmVhbSBv
 czI7DQogIG9zMiA8PCBzIDw8ICJfIiA8PCBpIDw8IHN0ZDo6ZW5kczsNCiAg
 Y29uc3Qgc3RkOjpzdHJpbmcgczIgPSBvczIuc3RyKCk7DQogIHN0ZDo6Y291
 dCA8PCAiMm5kIHN0cmluZyBzaXplID0gIiA8PCBzMi5zaXplKCkgPDwgc3Rk
 OjplbmRsOw0KICBjb25zdCBjaGFyKiBzYzIgPSBzMi5jX3N0cigpOw0KICBz
 dGQ6OmNvdXQgPDwgIjJuZCBDLXN0cmluZyBzaXplID0gIiA8PCBzdGQ6OnN0
 cmxlbiggc2MyICkgPDwgc3RkOjplbmRsOw0KICBzdGQ6OmNvdXQgPDwgczIg
 PDwgc3RkOjplbmRsOw0KICBzdGQ6OmNvdXQgPDwgc2MyIDw8IHN0ZDo6ZW5k
 bDsNCg0KICByZXR1cm4gMDsNCn0NCg==
 ---1970702844-1785715624-1037797285=:23333--

Re: libstdc++/8655: Problematic behaviour of std::ends

[paolo]

Synopsis: Problematic behaviour of std::ends

State-Changed-From-To: open->feedback
State-Changed-By: paolo
State-Changed-When: Wed Nov 20 04:50:29 2002
State-Changed-Why:
    Unfortunately, the attachment got lost. Could you possibly
    provide it again?

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8655

libstdc++/8655: Problematic behaviour of std::ends

[Ioannis.Papadopoulos]

>Number:         8655
>Category:       libstdc++
>Synopsis:       Problematic behaviour of std::ends
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Nov 20 02:46:46 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Ioannis.Papadopoulos@cern.ch
>Release:        3.2
>Organization:
>Environment:
Linux
>Description:
Funny behaviour of std::ends when using std::ostringstream

It looks as if a funny character is appended instead of \0
It creates serious problems when one has to extract a C-string.
>How-To-Repeat:
build, and run the attached example and the problems will manifest by themselves. Try to redirect the output to a file and open the file with emacs or nedit to see the funny character that ends inserts.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: