From: Jeff Johnston <jjohnstn@redhat.com>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Java Inferior Call Take 2
Date: Fri, 11 Jun 2004 17:49:00 -0000 [thread overview]
Message-ID: <40C9F09B.7080908@redhat.com> (raw)
In-Reply-To: <40A9264C.4060404@redhat.com>
Ping.
Jeff Johnston wrote:
> This is the reworked java inferior call patch. My previous attempt
> tried to modify the gdb v3 abi code to handle missing debug information
> from gcj. After a couple of gcc patches from Andrew Haley, the
> gnu-v3-abi.c code doesn't require any tampering.
>
> I had to enhance dwarf2read.c to handle the java vtable name (which is
> vtable) and to modify C++-only code to handle java syntax for class names.
>
> I have included a test case.
>
> Ok to commit?
>
> -- Jeff J.
>
> 2004-05-17 Jeff Johnston <jjohnstn@redhat.com>
>
> * dwarf2read.c (typename_concat): Change prototype to accept dwarf2_cu
> struct pointer as argument. Change function to use new argument to
> determine language. If language is Java, use "." as separator,
> otherwise, use "::".
> (partial_die_parent_scope): Change comment to include java. Check
> language to determine if Java "." or C++ "::" separator should be used.
> (add_partial_symbol): Enhance tests for C++ to also test for Java.
> (guess_structure_name): Ditto.
> (read_subroutine_type): Ditto.
> (new_symbol): Ditto.
> (dwarf2_add_member_fn): Add check for Java when reading member name.
> Java debug info includes full class name which must be stripped off.
> (read_structure_type): Add Java vtable support.
> (read_namespace): Add Java support.
> * jv-exp.y (FuncStart): New pattern.
> (MethodInvocation): Add support for simple function calls. Change
> warning message for other forms of inferior call currently not
> supported.
> * valarith.c (value_subscript): Treat an array with upper-bound
> of -1 as unknown size.
>
> gdb/testsuite/ChangeLog:
>
> 2004-05-17 Jeff Johnston <jjohnstn@redhat.com>
>
> * gdb.java/jprint.exp: New test for java inferior call.
> * gdb.java/jprint.java: Ditto.
>
next prev parent reply other threads:[~2004-06-11 17:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 20:53 Jeff Johnston
2004-06-11 17:49 ` Jeff Johnston [this message]
2004-06-17 3:06 ` Daniel Jacobowitz
2004-06-17 20:52 ` Jeff Johnston
2004-06-19 23:59 ` Daniel Jacobowitz
2004-06-21 10:49 ` Andrew Haley
2004-06-21 15:17 ` Andrew Haley
2004-06-23 11:06 ` Andrew Haley
2004-06-23 13:47 ` Daniel Jacobowitz
2004-06-23 16:06 ` Andrew Haley
2004-06-23 16:08 ` Daniel Jacobowitz
2004-06-23 21:55 ` Jeff Johnston
2004-06-23 23:01 ` Daniel Jacobowitz
2004-06-24 17:57 ` Tom Tromey
2004-07-06 21:47 ` Jeff Johnston
2004-07-26 19:49 ` Jeff Johnston
2004-07-26 19:51 ` Daniel Jacobowitz
2004-08-02 10:17 ` Andrew Haley
2004-08-02 15:17 ` Andrew Haley
2004-08-02 20:20 ` Daniel Jacobowitz
2004-08-03 18:45 ` Andrew Haley
2004-08-16 13:08 ` Andrew Haley
2004-08-16 13:18 ` Daniel Jacobowitz
2004-08-16 20:32 ` Daniel Jacobowitz
2004-08-16 20:35 ` Daniel Jacobowitz
2004-08-24 18:53 ` [RFA]: Java Inferior Call Take 3 Jeff Johnston
2004-08-24 19:05 ` Michael Chastain
2004-08-24 19:28 ` Jeff Johnston
2004-08-24 19:10 ` Michael Chastain
2004-08-24 19:48 ` Andrew Cagney
2004-09-01 4:51 ` Jim Blandy
2004-09-09 23:41 ` Jeff Johnston
2004-09-10 20:12 ` Jim Blandy
2004-09-15 22:58 ` Jeff Johnston
2004-09-20 18:23 ` Jim Blandy
2004-09-20 20:19 ` Jeff Johnston
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40C9F09B.7080908@redhat.com \
--to=jjohnstn@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox