This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Debug mode output broken

From: Paolo Carlini <pcarlini at suse dot de>
To: Jonathan Wakely <cow at compsoc dot man dot ac dot uk>
Cc: libstdc++ at gcc dot gnu dot org
Date: Fri, 06 Aug 2004 13:20:56 +0200
Subject: Re: Debug mode output broken
References: <15240.1091627368@www8.gmx.net> <20040806090629.GB80353@compsoc.man.ac.uk> <41134E51.8030909@suse.de> <20040806094127.GD80353@compsoc.man.ac.uk> <411353CA.7050301@suse.de> <20040806095730.GE80353@compsoc.man.ac.uk> <20040806100854.GF80353@compsoc.man.ac.uk> <20040806105704.GA86551@compsoc.man.ac.uk> <20040806111250.GA87840@compsoc.man.ac.uk>

Jonathan Wakely wrote:

An inadvertent change to a message that makes it longer than the
128-byte buffer would also cause an overflow. Badness.

You are definitely right. The real fix for this kind of very dangerous
problems involves changing the code to use an ostringstream. I think
it's time to do that.

Paolo.

References:
- Debug mode output broken
  - From: Kaspar Fischer
- Re: Debug mode output broken
  - From: Jonathan Wakely
- Re: Debug mode output broken
  - From: Paolo Carlini
- Re: Debug mode output broken
  - From: Jonathan Wakely
- Re: Debug mode output broken
  - From: Paolo Carlini
- Re: Debug mode output broken
  - From: Jonathan Wakely
- Re: Debug mode output broken
  - From: Jonathan Wakely
- Re: Debug mode output broken
  - From: Jonathan Wakely
- Re: Debug mode output broken
  - From: Jonathan Wakely

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]