From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4476 invoked by alias); 7 May 2002 20:29:01 -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 4465 invoked from network); 7 May 2002 20:29:00 -0000 Received: from unknown (HELO gash2.peakpeak.com) (207.174.178.17) by sources.redhat.com with SMTP; 7 May 2002 20:29:00 -0000 Received: from creche.cygnus.com (ta0202.peakpeak.com [204.144.244.202]) by gash2.peakpeak.com (8.9.3/8.9.3) with ESMTP id OAA16596; Tue, 7 May 2002 14:28:55 -0600 Received: (from tromey@localhost) by creche.cygnus.com (8.9.3/8.9.3) id OAA22013; Tue, 7 May 2002 14:38:42 -0600 To: Michael Snyder Cc: gdb-patches@sources.redhat.com, green@redhat.com Subject: Re: Patch: printing java `char' values References: <877kmh8a6r.fsf@creche.redhat.com> <3CD71722.DD3585A4@redhat.com> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom X-Zippy: Don't SANFORIZE me!! Date: Tue, 07 May 2002 13:29:00 -0000 In-Reply-To: Michael Snyder's message of "Mon, 06 May 2002 16:52:02 -0700" Message-ID: <87g013vgkt.fsf@creche.redhat.com> X-SW-Source: 2002-05/txt/msg00174.txt.bz2 >>>>> "Michael" == Michael Snyder writes: Michael> For future reference, the convention here is that "Patch" Michael> means "I've checked this in, I'm just letting you know". Michael> What you want is probably "RFC" (request for comment). Thanks. Michael> I'm not sure why that's happening, but it tickles my Michael> familiar-bone. Has someone else recently posted about Michael> something related to this? Maybe Per Bothner? I don't remember seeing anything about it, but then I only skim this list. >> The appended hack fixes the problem for me. I'm sure there is some >> better way to handle this, but I don't know what. Why would I end up >> with a TYPE_CODE_INT here? Michael> I agree that this is not the correct fix, but that it Michael> does help illustrate the problem. Unfortunately, I don't Michael> know who, if anyone, is actively maintaining Java these days. Nobody. I've spent a little time this week looking into the major Java annoyances (meaning: stuff that worked once but now doesn't) as time permits. Unfortunately my gdb time and knowledge are both limited. I was hoping someone would understand where the type comes from in this situation, so I could see if a more appropriate fix is available. Tom