[Bug c++/42022] takes segmentation fault at proxy file

2011-03-29 Thread redi at gcc dot gnu.org 
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42022

Jonathan Wakely redi at gcc dot gnu.org changed:

   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution||INVALID

--- Comment #3 from Jonathan Wakely redi at gcc dot gnu.org 2011-03-29 
17:00:47 UTC ---
(In reply to comment #2)
 
 This is focal to what development? I can't get any compiler to get it on 
 a 64 bit Intel/AMD how would Linux
 compile a variant when it can't do a fairly stable release?
 
  If the code seg faults anywhere in code execution why blame the 
 compiler with a code dump?
 
  How can I upgrade if the compiler was broke?

I don't understand your questions, but if you can't test a current release of
GCC then please report the bug to Mandriva.

In any case, noone can look at the problem without a testcase and the other
information listed at http://gcc.gnu.org/bugs/ so I'm closing this report.

If you reopen this report please provide the required information.

[Bug c++/42022] takes segmentation fault at proxy file

2009-11-12 Thread rguenth at gcc dot gnu dot org 


--- Comment #1 from rguenth at gcc dot gnu dot org  2009-11-12 23:22 ---
GCC 4.1.1 is no longer maintained, please update to at least GCC 4.3.4 and
reproduce the problem there.  We need preprocessed source to do anything
about it if the bug reproduces there.


-- 

rguenth at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |WAITING
Summary|takes segmentation fault at |takes segmentation fault at
   |proxy file  |proxy file


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42022

[Bug c++/42022] takes segmentation fault at proxy file

2009-11-12 Thread kholt at joimail dot com 


--- Comment #2 from kholt at joimail dot com  2009-11-12 23:54 ---
Subject: Re:  takes segmentation fault at proxy file

rguenth at gcc dot gnu dot org wrote:
 --- Comment #1 from rguenth at gcc dot gnu dot org  2009-11-12 23:22 
 ---
 GCC 4.1.1 is no longer maintained, please update to at least GCC 4.3.4 and
 reproduce the problem there.  We need preprocessed source to do anything
 about it if the bug reproduces there.


   
You are quick!   Who is watching?

This is focal to what development? I can't get any compiler to get it on 
a 64 bit Intel/AMD how would Linux
compile a variant when it can't do a fairly stable release?

 If the code seg faults anywhere in code execution why blame the 
compiler with a code dump?

 How can I upgrade if the compiler was broke?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42022