This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: Patch: printing java `char' values
- From: Tom Tromey <tromey at redhat dot com>
- To: Michael Snyder <msnyder at redhat dot com>
- Cc: gdb-patches at sources dot redhat dot com, green at redhat dot com
- Date: 07 May 2002 14:38:42 -0600
- Subject: Re: Patch: printing java `char' values
- References: <877kmh8a6r.fsf@creche.redhat.com> <3CD71722.DD3585A4@redhat.com>
- Reply-to: tromey at redhat dot com
>>>>> "Michael" == Michael Snyder <msnyder@redhat.com> 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