From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5783 invoked by alias); 4 Dec 2003 21:48:07 -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 5776 invoked from network); 4 Dec 2003 21:48:07 -0000 Received: from unknown (HELO barry.mail.mindspring.net) (207.69.200.25) by sources.redhat.com with SMTP; 4 Dec 2003 21:48:07 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by barry.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1AS1Jt-0000m2-00; Thu, 04 Dec 2003 16:47:33 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 7D0224B35C; Thu, 4 Dec 2003 16:47:28 -0500 (EST) To: gdb-patches@sources.redhat.com, weigand@i1.informatik.uni-erlangen.de Subject: Re: [PATCH] Fix some Java test case problems Cc: uweigand@de.ibm.com Message-Id: <20031204214728.7D0224B35C@berman.michael-chastain.com> Date: Thu, 04 Dec 2003 21:48:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2003-12/txt/msg00146.txt.bz2 Hi Ulrich, > various Java test cases were failing due to what appears to > be incorrect names in the test case. Right, there is a bit of a mess there. The old tests were written to accommodate the behavior of the demangler at the time. The demangler has been rewritten, and is still up in the air. In fact some more demangler fixes were checked in today. First could you check that you have a very current copy of libiberty, particularly libiberty/cp-demangle.c. Then, instead of a patch, file a gdb PR. Throw in the URL of your post to gdb-patches if you want. Then when the demangler settles down, and I get some time, I will overhaul the tests. Michael C