From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9941 invoked by alias); 18 Apr 2003 16:46:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 9926 invoked by uid 71); 18 Apr 2003 16:46:01 -0000 Date: Fri, 18 Apr 2003 16:46:00 -0000 Message-ID: <20030418164601.9924.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Woody LaRue" Subject: Re: debug/7360: g++ generates illegal debug info on Solaris that crashes gdb Reply-To: "Woody LaRue" X-SW-Source: 2003-04/txt/msg00841.txt.bz2 List-Id: The following reply was made to PR debug/7360; it has been noted by GNATS. From: "Woody LaRue" To: , , , , Cc: Subject: Re: debug/7360: g++ generates illegal debug info on Solaris that crashes gdb Date: Fri, 18 Apr 2003 09:42:58 -0700 I have been seeing the very same behavior when debugging SystemC models = compiled with gcc 3.2 using=20 gdb. This problem will soon become a great concern to the SystemC = community (which is currently using gcc 2.95, but will be upgrading to gcc 3.2) Are there any plans to fix this problem ? = I'm considering undertaking a fix and would greatly appreciate any pointers to get me started.=20 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&database=3D= gcc&pr=3D7360