From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8681 invoked by alias); 14 Apr 2005 16:15:45 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 7894 invoked from network); 14 Apr 2005 16:15:37 -0000 Received: from unknown (HELO e34.co.us.ibm.com) (32.97.110.132) by sourceware.org with SMTP; 14 Apr 2005 16:15:37 -0000 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e34.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j3EGFV5b481124 for ; Thu, 14 Apr 2005 12:15:36 -0400 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j3EGFSNP237270 for ; Thu, 14 Apr 2005 10:15:29 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j3EGFSYc010475 for ; Thu, 14 Apr 2005 10:15:28 -0600 Received: from austin.ibm.com (netmail2.austin.ibm.com [9.41.248.176]) by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j3EGFSUd010455 for ; Thu, 14 Apr 2005 10:15:28 -0600 Received: from lazy.austin.ibm.com (lazy.austin.ibm.com [9.53.94.97]) by austin.ibm.com (8.12.10/8.12.10) with ESMTP id j3EGFRen049048 for ; Thu, 14 Apr 2005 11:15:27 -0500 Date: Thu, 14 Apr 2005 16:15:00 -0000 From: Manoj Iyer X-X-Sender: manjo@lazy To: gdb-patches@sources.redhat.com Subject: Re: [RFC] GDB prints internal error with C++ application produced by XLC. In-Reply-To: <20050414030914.GA23471@nevyn.them.org> Message-ID: References: <20050414030832.GA23417@nevyn.them.org> <20050414030914.GA23471@nevyn.them.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2005-04/txt/msg00124.txt.bz2 Daniel, > > No, don't do that. Ok, that is good to know... :-) > By the way, I have since posted a more complete patch which should > obsolete this one. If you'd like, you could try it on your test. Which is fine by me, coz all I wanted was to see a fix for that error message. Did you include my patch in yours? Coz I remember a conversation where u had mentioned that you were waiting for my patch to makeit into the source base. Thanks Manjo