This non-program causes the same internal error in gcc 4.7.3 (with
-std=c++0x and -std=c++11). In general, it seems to happen any time I
push_back an object with an inaccessible copy constructor.
#include
class A {
A(const A&)=delete;
};
int main()
{
std::vector().push_back(*(A*)0);
Sorry everyone, I accidentally added this bug to the cupsys section. I
had arrived at this page by entering the bug number into the URL without
also changing the word "cupsys" in the URL. Then I misunderstood the
meaning of the "Also needs fixing here" button.
John-Paul
--
nm-applet crashed wi
Timo: If I recall correctly, Ben Hodgetts was right and the problem went
away after cleaning up a bunch of stuff. (Belated thanks, Ben!) I've
changed my setup significantly since then, so I can't confirm 100%. But
I am not currently experiencing the problem, and I never have
experienced it since
Maybe this will help. I have the same problem on my HP Pavilion dv8000
with a Radeon Xpress 200M. In my case, I've never been able to get 3D
working, but I expect that's an unrelated problem. 2D rendering slowed
down dramatically with my upgrade to Feisty.
I've attached the same information tha
