Bug#236912: [Bug libstdc++/14493] No std::bad_alloc::what() const

2004-03-08 Thread Matthias Klose
[resending for the inclusion to the Debian BTS] Phil Edwards writes: > close 236912 > thanks > > This bug report reinforces my opinion that bug reports consisting of > claims of nonconformance, but not accompanied by a testcase, should be > immediately closed. > > > On Mon, Mar 08, 2004 at 11:1

[Bug libstdc++/14493] No std::bad_alloc::what() const

2004-03-08 Thread doko at cs dot tu-berlin dot de
--- Additional Comments From doko at cs dot tu-berlin dot de 2004-03-09 05:19 --- Subject: Re: No std::bad_alloc::what() const [resending for the inclusion to the Debian BTS] Phil Edwards writes: > close 236912 > thanks > > This bug report reinforces my opinion that bug reports consi

[Bug libstdc++/14493] No std::bad_alloc::what() const

2004-03-08 Thread zack at gcc dot gnu dot org
--- Additional Comments From zack at gcc dot gnu dot org 2004-03-09 04:45 --- It appears to me that the original reporter wanted what() to return an "intelligible error message" a la icc's "bad allocation", rather than "St9bad_alloc" (which does communicate the same information but in a

Processed: Re: [Bug libstdc++/14493] No std::bad_alloc::what() const

2004-03-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > close 236912 Bug#236912: [PR 14493] new: No std::bad_alloc::what() const 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to "Jeroen T. Vermeulen" <[EMAIL PROTECTED]> > thanks Stopping

[Bug libstdc++/14493] No std::bad_alloc::what() const

2004-03-08 Thread pme at gcc dot gnu dot org
--- Additional Comments From pme at gcc dot gnu dot org 2004-03-09 04:14 --- Works just fine. Submitter is mistaken. -- What|Removed |Added Status|NEW

[Bug libstdc++/14493] No std::bad_alloc::what() const

2004-03-08 Thread phil at jaj dot com
--- Additional Comments From phil at jaj dot com 2004-03-09 04:14 --- Subject: Re: No std::bad_alloc::what() const close 236912 thanks This bug report reinforces my opinion that bug reports consisting of claims of nonconformance, but not accompanied by a testcase, should be immediately

Re: [Bug libstdc++/14493] No std::bad_alloc::what() const

2004-03-08 Thread Phil Edwards
close 236912 thanks This bug report reinforces my opinion that bug reports consisting of claims of nonconformance, but not accompanied by a testcase, should be immediately closed. On Mon, Mar 08, 2004 at 11:15:05PM -, bangerth at dealii dot org wrote: > For Andrew: the code takes the respect

[Bug debug/11983] [3.3 Regression] ICE in dwarf-2 on code using altivec

2004-03-08 Thread gdr at integrable-solutions dot net
--- Additional Comments From gdr at integrable-solutions dot net 2004-03-09 03:13 --- Subject: Re: [3.3 Regression] ICE in dwarf-2 on code using altivec "amodra at bigpond dot net dot au" <[EMAIL PROTECTED]> writes: | 3.4.0 fix committed. Could you commit correponding versions for gc

[Bug debug/11983] [3.3 Regression] ICE in dwarf-2 on code using altivec

2004-03-08 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2004-03-09 03:04 --- 3.4.0 fix committed. -- What|Removed |Added Known to work|3.3 3.5.0

Results for 3.3.3 (Debian 20040306) testsuite on s390-ibm-linux-gnu

2004-03-08 Thread Matthias Klose
LAST_UPDATED: Native configuration is s390-ibm-linux-gnu === g++ tests === Running target unix XPASS: g++.other/init5.C Execution test === g++ Summary === # of expected passes8181 # of unexpected successes 1 # of expected failures 93

Results for 3.3.3 (Debian 20040306) testsuite on mips-unknown-linux-gnu

2004-03-08 Thread Matthias Klose
LAST_UPDATED: Native configuration is mips-unknown-linux-gnu === g++ tests === Running target unix XPASS: g++.dg/other/packed1.C execution test XPASS: g++.law/profile1.C (test for excess errors) XPASS: g++.law/profile1.C Execution test XPASS: g++.other/init5.C Execution test

Results for 3.3.3 (Debian 20040306) testsuite on mipsel-unknown-linux-gnu

2004-03-08 Thread Matthias Klose
LAST_UPDATED: Native configuration is mipsel-unknown-linux-gnu === g++ tests === Running target unix XPASS: g++.law/profile1.C (test for excess errors) XPASS: g++.law/profile1.C Execution test XPASS: g++.other/init5.C Execution test === g++ Summary === # of e

[Bug libstdc++/14493] No std::bad_alloc::what() const

2004-03-08 Thread bangerth at dealii dot org
--- Additional Comments From bangerth at dealii dot org 2004-03-08 23:15 --- For Andrew: the code takes the respective method of the base class. Here's a testcase: --- #include #include int main () { try { new char[static_cast(-1)/2]; } cat

Processed: gcc: submitted Debian report #236912 to gcc-gnats as PR 14493

2004-03-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > # submitted Debian report #236912 to gcc-gnats as PR 14493 > # http://gcc.gnu.org/PR14493 > forwarded 236912 http://gcc.gnu.org/PR14493 Bug#236912: /usr/include/c++/3.3/new: No std::bad_alloc::what() const Noted your statement that Bug has been forwarde

[Bug libstdc++/14493] No std::bad_alloc::what() const

2004-03-08 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added Summary|new: No |No std::bad_alloc::what() |std::bad_alloc::what() const|const http://gcc.gnu.org/bugzilla/s

[Bug libstdc++/14493] new: No std::bad_alloc::what() const

2004-03-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-03-08 22:36 --- Confirmed a bug, but it seems like the code you have should compile as exception have a what() method. -- What|Removed |Added --

Bug#236912: /usr/include/c++/3.3/new: No std::bad_alloc::what() const

2004-03-08 Thread Jeroen T. Vermeulen
Package: libstdc++5-3.3-dev Version: 1:3.3.3-2 Severity: minor File: /usr/include/c++/3.3/new std::bad_alloc doesn't seem to define a what() (std par. 18.4.2.1) leading to unintelligible error messages. -- System Information: Debian Release: testing/unstable Architecture: powerpc (ppc) Kernel: Li

gcc-3.3_3.3.3ds5-2_hppa.changes ACCEPTED

2004-03-08 Thread Debian Installer
Accepted: cpp-3.3_3.3.3-2_hppa.deb to pool/main/g/gcc-3.3/cpp-3.3_3.3.3-2_hppa.deb fastjar_3.3.3-2_hppa.deb to pool/main/g/gcc-3.3/fastjar_3.3.3-2_hppa.deb fixincludes_3.3.3-2_hppa.deb to pool/main/g/gcc-3.3/fixincludes_3.3.3-2_hppa.deb g++-3.3_3.3.3-2_hppa.deb to pool/main/g/gcc-3.3/g++-3

Processing of gcc-3.3_3.3.3ds5-2_hppa.changes

2004-03-08 Thread Archive Administrator
gcc-3.3_3.3.3ds5-2_hppa.changes uploaded successfully to localhost along with the files: gcc-3.3-base_3.3.3-2_hppa.deb libgcc1_3.3.3-2_hppa.deb cpp-3.3_3.3.3-2_hppa.deb protoize_3.3.3-2_hppa.deb fixincludes_3.3.3-2_hppa.deb gobjc-3.3_3.3.3-2_hppa.deb libobjc1_3.3.3-2_hppa.deb gij-3.

Bug#235870: acknowledged by developer (Re: Bug#235870: gcc-3.3: support backtrace on ia64)

2004-03-08 Thread Branden Robinson
On Sat, Mar 06, 2004 at 12:18:07AM -0800, Debian Bug Tracking System wrote: > Branden Robinson writes: > > On Wed, Mar 03, 2004 at 11:02:15AM +0100, Matthias Klose wrote: > > > Branden Robinson writes: > > > > Package: gcc-3.3 > > > > Version: 1:3.3.3-0pre3 > > > > Severity: normal > > > > > > > >

Bug#236798: libstdc++6-dbg: package overlap with libstdc++5-3.3-dbg

2004-03-08 Thread Laurent Bonnaud
Package: libstdc++6-dbg Version: 3.4-0pre1 Severity: important Tags: experimental Hi, here is the problem: Unpacking libstdc++6-dbg (from .../libstdc++6-dbg_3.4-0pre1_i386.deb) ... dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/lib/debug/libstdc++.a', whi