From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27470 invoked by alias); 9 Sep 2008 23:36:38 -0000 Received: (qmail 27462 invoked by uid 22791); 9 Sep 2008 23:36:38 -0000 X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 09 Sep 2008 23:35:50 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id m89NZDbB015070 for ; Tue, 9 Sep 2008 19:35:33 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m89NZ2Gr006939 for ; Tue, 9 Sep 2008 19:35:02 -0400 Received: from lindt.uglyboxes.com (sebastian-int.corp.redhat.com [172.16.52.221]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id m89NYwHr023567; Tue, 9 Sep 2008 19:34:59 -0400 Message-ID: <48C70822.3070905@redhat.com> Date: Tue, 09 Sep 2008 23:36:00 -0000 From: Keith Seitz User-Agent: Thunderbird 2.0.0.14 (X11/20080421) MIME-Version: 1.0 To: tromey@redhat.com CC: gdb@sourceware.org Subject: Re: Some java questions References: <48C6D1DF.3060705@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-09/txt/msg00059.txt.bz2 Tom Tromey wrote: > To support Java 1.5, we had to add return types to name mangling. > These are needed due to covariant return types. Ah, okay, that explains a lot. > What you are seeing here is just how the demangler chooses to print > this information. E.g., when I 'nm --demangle=java' a simple java > program, I see: > > 0804891e T h.main(java.lang.String[])void > U java.lang.Object.toString()java.lang.String > [etc] Yuck. Nonetheless, it looks like that's the status quo, and I need to fix it. I'll also look into either fixing the "info func" printout or at least add a test case for that so that it doesn't disappear. Keith