Bug#516727: gcc segfaults on simple wrong c++ code

2009-02-23 Thread Rutger ter Borg
Package: g++ (Debian 4.3.3-4) 4.3.3 The current c++ compiler segfaults on the following simple code mistake, where a destructor doesn't have the same id as that the class. template< typename T > class some_class { some_class() {} // segfault ~some() {} // no segfault //

Processed: Re: Bug#516727: gcc segfaults on simple wrong c++ code

2009-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 516727 g++-4.3 Bug#516727: gcc segfaults on simple wrong c++ code Warning: Unknown package 'debian' Warning: Unknown package '4.3.3-4' Warning: Unknown package '4.3.3' Bug reassigned from package `g++ (debian 4.3.3-4) 4.3.3' to `g++-4.3'.

Bug#516727: gcc segfaults on simple wrong c++ code

2009-02-23 Thread Martin Michlmayr
* Rutger ter Borg [2009-02-23 12:14]: > Package: g++ (Debian 4.3.3-4) 4.3.3 > > The current c++ compiler segfaults on the following simple code mistake, > where > a destructor doesn't have the same id as that the class. Confirmed. Note that this didn't happen with 4.3.3-1 -- Martin Michlmayr

Bug#516727: gcc segfaults on simple wrong c++ code

2009-02-23 Thread Martin Michlmayr
..4.3-2009-02-23-r144380/gcc] ./g++ -v Using built-in specs. Target: x86_64-unknown-linux-gnu Configured with: /home/tbm/scratch/gcc-4.3/configure --disable-bootstrap --enable-languages=c,c++ Thread model: posix gcc version 4.3.4 20090223 (prerelease) (GCC) -- Martin Michlmayr http://www.cyrius

Bug#516419: marked as done (ppl_0.10-3(mips/unstable):)

2009-02-23 Thread Debian Bug Tracking System
Your message dated Mon, 23 Feb 2009 14:40:45 +0100 with message-id <20090223134045.ga...@l04.local> and subject line Re: Bug#516419: ppl_0.10-3(mips/unstable): has caused the Debian Bug report #516419, regarding ppl_0.10-3(mips/unstable): to be marked as done. This means that you claim that the p

Processed: [bts-link] source package gcc-defaults

2009-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package gcc-defaults > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.deb

[bts-link] source package gcc-defaults

2009-02-23 Thread bts-link-upstream
# # bts-link upstream status pull for source package gcc-defaults # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #231748 # * http://gcc.gnu.org/PR11931 # * remote status changed: NEW -> RESOLV

Bug#516862: optimization can prevent terminate() from being called on throw from destructor while unwinding

2009-02-23 Thread Timothy Brownawell
Package: g++-4.3 Version: 4.3.2-1.1 , 4.3.3-4 This is also in at least g++-4.1 (4.1.2-25 and 4.1.1-21) and g++-4.2 (4.2.4-6). I don't have a g++-3.x installed to test with. This is on i386. The program at the end of this report should always print "my_terminate()" and exit. If the "WTF dont_cal