This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: java/1413: gdb loses java type information
- From: Tom Tromey <tromey at redhat dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 9 Oct 2003 19:08:00 -0000
- Subject: Re: java/1413: gdb loses java type information
- Reply-to: Tom Tromey <tromey at redhat dot com>
The following reply was made to PR java/1413; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-gnats@sources.redhat.com
Subject: Re: java/1413: gdb loses java type information
Date: 09 Oct 2003 12:58:16 -0600
Jim> Are there cases where treating every object according to its dynamic
Jim> type would change the semantics of an expression, aside from making
Jim> more expressions permissible (while still never accepting non-typesafe
Jim> expressions)?
The only case I can think of is when a class has a field with the
same name as a field in one of its ancestors.
This is pretty unusual though. I don't know of a situation like this
in libgcj, for instance -- whereas I run into the other debugging
problem very frequently.
Tom