Re: Bug#126162: [sparc] unable to build gcc-3.0.3-1
Ben Collins writes:
> On Sun, Dec 23, 2001 at 03:03:01AM +0100, Matthias Klose wrote:
> > >
> > > That's the problem...let me remove that package and put this bug on
> > > binutils-multiarch. Try the build again Matthias.
> >
> > ok, the latter problem went away, however I still get the regressions
> > (bus errors) for every c++ executable. logs in the same location.
> >
>
> Ok, I thought there was a fix for this commited to gcc CVS. Did you get
> it with your checkout? Was it maybe comitted to trunk and not the 3.0
> branch?
the Debian source contains the 3.0.3 tarball as released
upstream. Which patch do you mean?
we fulfill the requirements mentioned in gcc/doc/install.texi:
sparc-*-linux*
GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
or newer on this platform. All earlier binutils and glibc
releases mishandled unaligned relocations on @code{sparc-*-*} targets.
gcc-2.95_2.95.4.ds7-0.011223_i386.changes INSTALLED
Installing: chill-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-0.011223_i386.deb cpp-2.95-doc_2.95.4-0.011223_all.deb to pool/main/g/gcc-2.95/cpp-2.95-doc_2.95.4-0.011223_all.deb cpp-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-0.011223_i386.deb g++-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/g++-2.95_2.95.4-0.011223_i386.deb g77-2.95-doc_2.95.4-0.011223_all.deb to pool/main/g/gcc-2.95/g77-2.95-doc_2.95.4-0.011223_all.deb g77-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/g77-2.95_2.95.4-0.011223_i386.deb gcc-2.95-doc_2.95.4-0.011223_all.deb to pool/main/g/gcc-2.95/gcc-2.95-doc_2.95.4-0.011223_all.deb gcc-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/gcc-2.95_2.95.4-0.011223_i386.deb gcc-2.95_2.95.4.ds7-0.011223.diff.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds7-0.011223.diff.gz gcc-2.95_2.95.4.ds7-0.011223.dsc to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds7-0.011223.dsc gcc-2.95_2.95.4.ds7.orig.tar.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds7.orig.tar.gz gobjc-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/gobjc-2.95_2.95.4-0.011223_i386.deb gpc-2.95-doc_2.95.4-0.011223_all.deb to pool/main/g/gcc-2.95/gpc-2.95-doc_2.95.4-0.011223_all.deb gpc-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/gpc-2.95_2.95.4-0.011223_i386.deb libg++2.8.1.3-dbg_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dbg_2.95.4-0.011223_i386.deb libg++2.8.1.3-dev_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dev_2.95.4-0.011223_i386.deb libg++2.8.1.3-glibc2.2_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-glibc2.2_2.95.4-0.011223_i386.deb libstdc++2.10-dbg_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-dbg_2.95.4-0.011223_i386.deb libstdc++2.10-dev_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-dev_2.95.4-0.011223_i386.deb libstdc++2.10-glibc2.2_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-0.011223_i386.deb protoize-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/protoize-2.95_2.95.4-0.011223_i386.deb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 118227 118754 Thank you for your contribution to Debian.
Bug#118227: marked as done (chill-2.95: Inconsistent spelling)
Your message dated Sun, 23 Dec 2001 14:59:14 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#118227: fixed in gcc-2.95 2.95.4.ds7-0.011223 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 4 Nov 2001 11:00:08 + >From [EMAIL PROTECTED] Sun Nov 04 05:00:08 2001 Return-path: <[EMAIL PROTECTED]> Received: from p3ee3aa70.dip.t-dialin.net (salem.getuid.de) [62.227.170.112] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 160L0a-0007Vx-00; Sun, 04 Nov 2001 05:00:08 -0600 Received: by salem.getuid.de (Postfix, from userid 1000) id D2B72E5A0; Sun, 4 Nov 2001 11:30:46 +0100 (CET) Date: Sun, 4 Nov 2001 11:30:46 +0100 From: Christian Kurz <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: chill-2.95: Inconsistent spelling Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23.1i X-Reportbug-Version: 1.33 Organization: set_eugid(getuid(), getgid()) Mail-Copies-To: never Delivered-To: [EMAIL PROTECTED] Package: chill-2.95 Version: N/A; reported 2001-11-04 Severity: minor Hi, you are writing "Chill" in the package description to refer to this package, but the package "chill" talks about "CHILL". Would you mind either also using CHILL instead of Chill or change the "chill" package? Thanks. Christian -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux salem.getuid.de 2.4.13-ac4 #1 Mon Oct 29 11:36:26 CET 2001 i586 Locale: LANG=POSIX, [EMAIL PROTECTED] -- He who knows that enough is enough will always have enough. -- Lao Tsu --- Received: (at 118227-close) by bugs.debian.org; 23 Dec 2001 20:11:30 + >From [EMAIL PROTECTED] Sun Dec 23 14:11:30 2001 Return-path: <[EMAIL PROTECTED]> Received: from auric.debian.org [206.246.226.45] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 16IEy2-0006KY-00; Sun, 23 Dec 2001 14:11:30 -0600 Received: from troup by auric.debian.org with local (Exim 3.12 1 (Debian)) id 16IEmA-0003Ol-00; Sun, 23 Dec 2001 14:59:14 -0500 From: Matthias Klose <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.66 $ Subject: Bug#118227: fixed in gcc-2.95 2.95.4.ds7-0.011223 Message-Id: <[EMAIL PROTECTED]> Sender: James Troup <[EMAIL PROTECTED]> Date: Sun, 23 Dec 2001 14:59:14 -0500 Delivered-To: [EMAIL PROTECTED] We believe that the bug you reported is fixed in the latest version of gcc-2.95, which has been installed in the Debian FTP archive: chill-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-0.011223_i386.deb cpp-2.95-doc_2.95.4-0.011223_all.deb to pool/main/g/gcc-2.95/cpp-2.95-doc_2.95.4-0.011223_all.deb cpp-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-0.011223_i386.deb g++-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/g++-2.95_2.95.4-0.011223_i386.deb g77-2.95-doc_2.95.4-0.011223_all.deb to pool/main/g/gcc-2.95/g77-2.95-doc_2.95.4-0.011223_all.deb g77-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/g77-2.95_2.95.4-0.011223_i386.deb gcc-2.95-doc_2.95.4-0.011223_all.deb to pool/main/g/gcc-2.95/gcc-2.95-doc_2.95.4-0.011223_all.deb gcc-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/gcc-2.95_2.95.4-0.011223_i386.deb gcc-2.95_2.95.4.ds7-0.011223.diff.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds7-0.011223.diff.gz gcc-2.95_2.95.4.ds7-0.011223.dsc to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds7-0.011223.dsc gcc-2.95_2.95.4.ds7.orig.tar.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds7.orig.tar.gz gobjc-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/gobjc-2.95_2.95.4-0.011223_i386.deb gpc-2.95-doc_2.95.4-0.011223_all.deb to pool/main/g/gcc-2.95/gpc-2.95-doc_2.95.4-0.011223_all.deb gpc-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/gpc-2.95_2.95.4-0.011223_i386.deb libg++2.8.1.3-dbg_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dbg_2.95.4-0.011223_i386.deb libg++2.8.1.3-dev_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dev_2.95.4-0.011223_i386.deb libg++2.8.1.3-glibc2.2_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-glibc2.2_2.95.4-0.011223_i386.deb libstdc++2.10-dbg_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-dbg_2.95.4-0.011223_i386.deb libstdc++2.10-dev_2.95.4-0.011223_i386.deb to p
Bug#118754: marked as done (gcc-2.95 doesn't build chill on m68k anymore)
Your message dated Sun, 23 Dec 2001 14:59:14 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#118754: fixed in gcc-2.95 2.95.4.ds7-0.011223 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 8 Nov 2001 16:08:50 + >From [EMAIL PROTECTED] Thu Nov 08 10:08:50 2001 Return-path: <[EMAIL PROTECTED]> Received: from sol.wohnheim.uni-ulm.de [134.60.220.1] (root) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 161rjW-00086P-00; Thu, 08 Nov 2001 10:08:50 -0600 Received: from caemlyn.wohnheim.uni-ulm.de ([EMAIL PROTECTED] [134.60.220.17]) by sol.wohnheim.uni-ulm.de (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id RAA17004 for <[EMAIL PROTECTED]>; Thu, 8 Nov 2001 17:08:48 +0100 X-Authentication-Warning: sol.wohnheim.uni-ulm.de: Host [EMAIL PROTECTED] [134.60.220.17] claimed to be caemlyn.wohnheim.uni-ulm.de Received: from michael by caemlyn.wohnheim.uni-ulm.de with local (Exim 3.32 #1 (Debian)) id 161rjU-0001id-00 for <[EMAIL PROTECTED]>; Thu, 08 Nov 2001 17:08:48 +0100 Date: Thu, 8 Nov 2001 17:08:48 +0100 To: [EMAIL PROTECTED] Subject: gcc-2.95 doesn't build chill on m68k anymore Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i From: Michael Fedrowitz <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] Package: gcc-2.95 Version: 2.95.4.ds6-0.011006 Severity: normal Hi, some time ago gcc-2.95 stopped building chill on m68k for no apparent reason (can't find anything in the changelog). chill has always built fine on m68k, and still does, so I don't really see a reason to disable it. Anyway, if there really is a good reason, then gcc-defaults shouldn't build a chill package for m68k anymore either. -Michael --- Received: (at 118754-close) by bugs.debian.org; 23 Dec 2001 20:11:31 + >From [EMAIL PROTECTED] Sun Dec 23 14:11:31 2001 Return-path: <[EMAIL PROTECTED]> Received: from auric.debian.org [206.246.226.45] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 16IEy3-0006Kg-00; Sun, 23 Dec 2001 14:11:31 -0600 Received: from troup by auric.debian.org with local (Exim 3.12 1 (Debian)) id 16IEmA-0003On-00; Sun, 23 Dec 2001 14:59:14 -0500 From: Matthias Klose <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.66 $ Subject: Bug#118754: fixed in gcc-2.95 2.95.4.ds7-0.011223 Message-Id: <[EMAIL PROTECTED]> Sender: James Troup <[EMAIL PROTECTED]> Date: Sun, 23 Dec 2001 14:59:14 -0500 Delivered-To: [EMAIL PROTECTED] We believe that the bug you reported is fixed in the latest version of gcc-2.95, which has been installed in the Debian FTP archive: chill-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-0.011223_i386.deb cpp-2.95-doc_2.95.4-0.011223_all.deb to pool/main/g/gcc-2.95/cpp-2.95-doc_2.95.4-0.011223_all.deb cpp-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-0.011223_i386.deb g++-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/g++-2.95_2.95.4-0.011223_i386.deb g77-2.95-doc_2.95.4-0.011223_all.deb to pool/main/g/gcc-2.95/g77-2.95-doc_2.95.4-0.011223_all.deb g77-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/g77-2.95_2.95.4-0.011223_i386.deb gcc-2.95-doc_2.95.4-0.011223_all.deb to pool/main/g/gcc-2.95/gcc-2.95-doc_2.95.4-0.011223_all.deb gcc-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/gcc-2.95_2.95.4-0.011223_i386.deb gcc-2.95_2.95.4.ds7-0.011223.diff.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds7-0.011223.diff.gz gcc-2.95_2.95.4.ds7-0.011223.dsc to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds7-0.011223.dsc gcc-2.95_2.95.4.ds7.orig.tar.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds7.orig.tar.gz gobjc-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/gobjc-2.95_2.95.4-0.011223_i386.deb gpc-2.95-doc_2.95.4-0.011223_all.deb to pool/main/g/gcc-2.95/gpc-2.95-doc_2.95.4-0.011223_all.deb gpc-2.95_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/gpc-2.95_2.95.4-0.011223_i386.deb libg++2.8.1.3-dbg_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dbg_2.95.4-0.011223_i386.deb libg++2.8.1.3-dev_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dev_2.95.4-0.011223_i386.deb libg++2.8.1.3-glibc2.2_2.95.4-0.011223_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-glibc2.2_2.95.4-0.011223_i386.deb libstdc++2.10-dbg_2.95.4-0.01
Bug#109073: marked as done (stringstream adds extra characters at the end)
Your message dated Sun, 23 Dec 2001 23:55:10 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in libstdc++2.10-glibc2.2-2.95.4-0.011223
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
Received: (at submit) by bugs.debian.org; 17 Aug 2001 21:27:23 +
>From [EMAIL PROTECTED] Fri Aug 17 16:27:23 2001
Return-path: <[EMAIL PROTECTED]>
Received: from (mail.grossprofit.com) [12.151.134.178]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 15Xr9D-0007wJ-00; Fri, 17 Aug 2001 16:27:19 -0500
Received: from profitlogic.com (dkatz.grossprofit.com [10.0.2.71]) by
mail.grossprofit.com with SMTP (Microsoft Exchange Internet Mail Service
Version 5.5.2653.13)
id NXWP17D3; Fri, 17 Aug 2001 17:26:06 -0400
Received: by profitlogic.com (sSMTP sendmail emulation); Fri, 17 Aug 2001
17:26:48 -0400
Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: stringstream adds extra characters at the end
From: Daniel Katz <[EMAIL PROTECTED]>
Date: 17 Aug 2001 17:26:47 -0400
Message-ID: <[EMAIL PROTECTED]>
Lines: 95
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
Package: libstdc++2.10-dev
Version: 2.95.4-0.010810
When I upgraded from 2.95.4-0.010424, I found that code which used
stringstreams (or istringstreams or ostringstreams) broke. In
particular, I find that extra characters are added to the end of the
stream which complicate reading and writing. For example, I wrote the
following program:
#include
#include
void
writer(int i)
{
static stringstream sstr;
// shove some stuff into the stringstream
sstr << "This is a fubar test. " << i;
sstr.unsetf(ios::skipws); // keep spaces
char c = 'Q'; // A throwaway that appears nowhere in the message
while (sstr >> c)
{
// print out each character and its hex representation. It
// should stop printing out when the end of the string is
// reached.
cout << c << "[" << hex << static_cast(c) << "] ";
c = 'Q';
}
cout << "\n" << endl ;
// reset the stringstream after it has gone out of good state
sstr.clear();
}
int
main()
{
for (int i = 0; i != 2; ++i)
{
writer(i);
}
return 0;
}
which returns the following under 2.95.4-0.010810:
T:54 h:68 i:69 s:73 :20 i:69 s:73 :20 a:61 :20 f:66 u:75 b:62 a:61 r:72 :20
t:74 e:65 s:73 t:74 .:2e :20 0:30 :0 :0 :0 :0 :0 :0 :0 :0
a:61 :20 f:66 u:75 b:62 a:61 r:72 :20 t:74 e:65 s:73 t:74 .:2e :20 1:31 :0
:0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0
while 2.95.4-0.010424 gives the correct (I think):
T:54 h:68 i:69 s:73 :20 i:69 s:73 :20 a:61 :20 f:66 u:75 b:62 a:61 r:72 :20
t:74 e:65 s:73 t:74 .:2e :20 0:30
T:54 h:68 i:69 s:73 :20 i:69 s:73 :20 a:61 :20 f:66 u:75 b:62 a:61 r:72 :20
t:74 e:65 s:73 t:74 .:2e :20 1:31
Note the trailing null characters in the 2.95.4-0.010810 version, and
notice also that the number of trailing nulls in the first half of the
output (8) exactly corresponds to the number of characters missing
from the string in the second half ("This is ").
Note that other tests we have done involving streaming in and out
numerical types have resulted in non-null characters being added at
the end. It is not only nulls which can be added, although only nulls
seem to be added in this particular case.
I am submitting this to Debian rather than to gcc since it is not
obvious to me whether this is a problem with the packaging or the
source. If the latter, would you please forward this report to the
gcc folks?
Thanks.
Dan Katz
---
Received: (at 109073-done) by bugs.debian.org; 23 Dec 2001 23:00:16 +
>From [EMAIL PROTECTED] Sun Dec 23 17:00:16 2001
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
Bug#115978: marked as done (stringstream adds extra characters at the end (forwarded from libstdc++2.10-dev))
Your message dated Sun, 23 Dec 2001 23:55:10 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in libstdc++2.10-glibc2.2-2.95.4-0.011223
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
Received: (at submit) by bugs.debian.org; 17 Oct 2001 15:06:39 +
>From [EMAIL PROTECTED] Wed Oct 17 10:06:39 2001
Return-path: <[EMAIL PROTECTED]>
Received: from (mail.grossprofit.com) [12.151.134.178]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 15tsHG-0007bI-00; Wed, 17 Oct 2001 10:06:38 -0500
Received: from profitlogic.com (godel.grossprofit.com [10.0.2.69]) by
mail.grossprofit.com with SMTP (Microsoft Exchange Internet Mail Service
Version 5.5.2653.13)
id 4G4NW428; Wed, 17 Oct 2001 11:06:08 -0400
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 17 Oct 2001 11:06:08 -0400
From: Justin Hahn <[EMAIL PROTECTED]>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011015
X-Accept-Language: en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: stringstream adds extra characters at the end (forwarded from
libstdc++2.10-dev)
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
Package: libstdc++2.10-glibc2.2
Version: 2.95.4-0.011006
Severity: critical
One of my users reported the following as Bug #109073. Unfortunately, he
reported it to libstdc++-dev, not realizing this is a code and not a
header issue. This is most likely an upstream problem. It is also
CRITICAL as it is preventing us from updating development systems (we're
stuck at 2.95.4-010424). While the original report was against
2.95.4-010810 we've been experiencing with this with every version newer
than 2.95.4-010424.
The original message follows this line:
When I upgraded from 2.95.4-0.010424, I found that code which used
stringstreams (or istringstreams or ostringstreams) broke. In
particular, I find that extra characters are added to the end of the
stream which complicate reading and writing. For example, I wrote the
following program:
#include
#include
void
writer(int i)
{
static stringstream sstr;
// shove some stuff into the stringstream
sstr << "This is a fubar test. " << i;
sstr.unsetf(ios::skipws); // keep spaces
char c = 'Q'; // A throwaway that appears nowhere in the message
while (sstr >> c)
{
// print out each character and its hex representation. It
// should stop printing out when the end of the string is
// reached.
cout << c << "[" << hex << static_cast(c) << "] ";
c = 'Q';
}
cout << "\n" << endl ;
// reset the stringstream after it has gone out of good state
sstr.clear();
}
int
main()
{
for (int i = 0; i != 2; ++i)
{
writer(i);
}
return 0;
}
which returns the following under 2.95.4-0.010810:
T:54 h:68 i:69 s:73 :20 i:69 s:73 :20 a:61 :20 f:66 u:75 b:62 a:61 r:72 :20
t:74 e:65 s:73 t:74 .:2e :20 0:30 :0 :0 :0 :0 :0 :0 :0 :0
a:61 :20 f:66 u:75 b:62 a:61 r:72 :20 t:74 e:65 s:73 t:74 .:2e :20 1:31 :0
:0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0
while 2.95.4-0.010424 gives the correct (I think):
T:54 h:68 i:69 s:73 :20 i:69 s:73 :20 a:61 :20 f:66 u:75 b:62 a:61 r:72 :20
t:74 e:65 s:73 t:74 .:2e :20 0:30
T:54 h:68 i:69 s:73 :20 i:69 s:73 :20 a:61 :20 f:66 u:75 b:62 a:61 r:72 :20
t:74 e:65 s:73 t:74 .:2e :20 1:31
Note the trailing null characters in the 2.95.4-0.010810 version, and
notice also that the number of trailing nulls in the first half of the
output (8) exactly corresponds to the number of characters missing
from the string in the second half ("This is ").
Note that other tests we have done involving streaming in and out
numerical types have resulted in non-null characters being added at
the end. It is not only nulls which can be added, although only nulls
Bug#120333: C++ Exception handlin on mips [was Re: Mozilla...]
severity 120333 important thanks Florian Lohoff writes: > On Thu, Dec 20, 2001 at 06:59:07PM +0100, Guido Guenther wrote: > > On Thu, Dec 20, 2001 at 06:47:17PM +0100, Matthias Klose wrote: > > > Is this a problem, that you can work around using g++-3.0 on mips? I > > > see the menu package up to date for mips. just wanting to reduce the > > > severity of the report from `grave' to `important'. > > Building with g++-3.0 fixes the problem - at least for the menu package. > > But I don't know if switching to g++-3.0 as default c++ compiler for > > mips is a good idea, since I have not used it much yet. > > As more people are installing debian-mips/mipsel we probably should to > a gcc 3.0 upload manually as this at least stops people from reporting > the bug and beeing stuck with a broken installation. lowering the severity, as there is a workaround available for the `menu' package.
Processed: Re: C++ Exception handlin on mips [was Re: Mozilla...]
Processing commands for [EMAIL PROTECTED]: > severity 120333 important Bug#120333: [mips] update-menus gets Bus Error Severity set to `important'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#126316: gcc-2.95: version 1:2.95.4-0.011223 dated 20010522 ?
Package: gcc-2.95 Version: 1:2.95.4-0.011223 Severity: minimal The description says that the version of the package is from May 2001, while version suggests it's from December 2001. It would be great if the description was fixed to make it clear and explained what version of GCC the package is. Thanks, - Peter.
Processed: 126316: minimal -> minor
Processing commands for [EMAIL PROTECTED]: > Severity 126316 minor Bug#126316: gcc-2.95: version 1:2.95.4-0.011223 dated 20010522 ? Severity set to `minor'. > Thanks, Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
