From: David Daney <ddaney.cavm@gmail.com>
To: Tom Tromey <tromey@redhat.com>,
Michael Haupt <michael.haupt@oracle.com>
Cc: java@gcc.gnu.org
Subject: Re: gcj and debugging
Date: Sat, 09 Feb 2013 00:38:00 -0000 [thread overview]
Message-ID: <51159A78.9030204@gmail.com> (raw)
In-Reply-To: <87y5f0ufko.fsf@fleche.redhat.com>
On 02/07/2013 10:47 AM, Tom Tromey wrote:
>>>>>> "Michael" == Michael Haupt <michael.haupt@oracle.com> writes:
>
> Michael> in a research project, I'm generating DWARF debugging info for machine
> Michael> code generated from Java. I looked at some of the DWARF debug info
> Michael> generated by gcj (including that contained in libgcj.so).
>
> I think the first thing to realize is that the gdb support for Java was
> all written to target gcj specifically, and also written long ago and
> then barely updated.
>
> It isn't very general or done the way it would be done now.
> It was never updated for the gcj binary compatibility ABI.
>
> Michael> Java arrays are all merely declared in the DWARF; structural
> Michael> information about Java array objects is not given. In libgcj's
> Michael> array.h, there are two classes, __JArray and JArray<T> (inheriting
> Michael> from __Jarray), that hold a length field and, in addition, a T*
> Michael> array[0].
>
> Michael> The debug info for libgcj does not contain any structural information
> Michael> about these two classes.
>
> Michael> How does gdb determine that there is a length field, and how many
> Michael> elements there are if the length is assigned dynamically? I reckon the
> Michael> latter can be done by describing the length as a DWARF exprloc, but
> Michael> the description is nowhere to be found.
>
> I thought things like "print array[0]" used to work, but even that seems
> to fail for me now. There is definitely some code for this in gdb, see
> jv-valprint.c:java_value_print. It seems to know a bit about array
> layout and then goes from there (though the code looks somewhat bogus to
> me...). See also jv-lang.c:evaluate_subexp_java for the code that tries
> to do array subscripting.
>
> Without debugging more I couldn't say why it is broken.
>
> Michael> How does the DWARF description of a Java array look?
> Michael> Is this generated at run-time somehow?
> Michael> Do gcj-generated binaries and gdb interact in some other ways than
> Michael> through DWARF when it comes to meta-info exchange?
>
> I believe gdb can also read some of the gcj runtime metadata and
> construct type information from this. The code here seems pretty
> minimal though.
>
> Michael> Likewise, how does gdb know how to display a java.lang.String as a,
> Michael> well, string?
>
> gdb has special code for this. It looks for a type named
> "java.lang.String" and then knows what fields it has.
>
Yes. IIRC, from gdb you have to do: call degug_????
The exact names of the debug helpers escape me at the moment.
David Daney
> Yucky.
>
> Nowadays I'd be more tempted to implement string-printing using Python.
> _Jv_Utf8Const could be handled this way too.
>
> Tom
>
>
next prev parent reply other threads:[~2013-02-09 0:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 15:10 Michael Haupt
2013-02-01 17:26 ` Andrew Haley
2013-02-07 18:47 ` Tom Tromey
2013-02-09 0:38 ` David Daney [this message]
2013-02-11 16:26 ` Michael Haupt
2013-02-11 16:32 ` Andrew Haley
2013-02-11 16:47 ` Michael Haupt
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=51159A78.9030204@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=java@gcc.gnu.org \
--cc=michael.haupt@oracle.com \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).