This is the mail archive of the
mailing list for the Java project.
Re: Is serialization broken?
- To: Bryce McKinlay <bryce at albatross dot co dot nz>
- Subject: Re: Is serialization broken?
- From: Tom Tromey <tromey at redhat dot com>
- Date: 26 Jan 2001 21:13:40 -0700
- Cc: Warren Levy <warrenl at redhat dot com>, Barnet Wagman <wagman at enteract dot com>, "java-discuss at sources dot redhat dot com" <java-discuss at sources dot redhat dot com>
- References: <Pine.LNX.firstname.lastname@example.org> <3A721BFC.586FA977@albatross.co.nz>
- Reply-To: tromey at redhat dot com
>>>>> "Bryce" == Bryce McKinlay <email@example.com> writes:
Bryce> Hmm... do you have a magic GDB that can demange new-ABI java
Bryce> symbols? I'm using the latest gdb from cvs, which seems to work
Bryce> quite nicely, but it doesn't demangle. I was planning to make
Bryce> an attempt to fix this, but don't want to duplicate someone
Bryce> elses effort.
I think there's been some discussion of this recently on the gdb list.
Anyway I know the gdb hackers are aware of it, and hopefully they are
taking care of it.
Java support in gdb is still only so-so, IMHO. I still find it
occasionally annoying to debug Java code. For instance, you can't
print a String from a C++ frame because you get "unknown type".
That's been a bug for years now.