From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13511 invoked by alias); 1 Mar 2004 20:49:54 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 13493 invoked by uid 48); 1 Mar 2004 20:49:53 -0000 Date: Mon, 01 Mar 2004 20:49:00 -0000 From: "konqueror at gmx dot de" To: gcc-bugs@gcc.gnu.org Message-ID: <20040301204948.14372.konqueror@gmx.de> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug java/14372] New: MIRANDA bug in java.net.URLConnection X-Bugzilla-Reason: CC X-SW-Source: 2004-03/txt/msg00160.txt.bz2 List-Id: I think I found another instance of the Miranda bug. With the attached patch applied to gcc trunk CVS and executing the attached testcase app the wrong "String getHeaderField(int index)" (the one in java.net.URLConnection) method gets called, instead of the one in gnu.java.net.protocol.http.Connection. Connection is a subclass of java.net.HttpURLConnection which is a subclass of java.net.URLConnection. You can see that the bug occurs when the testapp prints a line with "BUT, WHY HERE". It was written by Rutger Ovidius . The patch attached applies to current 3.4.0 cvs tree too and triggers the same bug. The bug doesnt trigger to 3.3.3 and the patch doesnt apply to it (I think). The bug gets only triggered with the patch applied. -- Summary: MIRANDA bug in java.net.URLConnection Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: java AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: konqueror at gmx dot de CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14372