From: Michael Haupt <michael.haupt@oracle.com>
To: "java@gcc.gnu.org" <java@gcc.gnu.org>
Subject: Re: gcj and debugging
Date: Mon, 11 Feb 2013 16:47:00 -0000 [thread overview]
Message-ID: <0CF78145-71B2-43BC-BA56-DFE2159779FE@oracle.com> (raw)
In-Reply-To: <51191D25.20407@redhat.com>
Andrew,
Am 11.02.2013 um 17:32 schrieb Andrew Haley <aph@redhat.com>:
> The Right Way to do it, as is done with the thread library, is to have
> a target library that GDB opens which contains accessor methods for all
> of the VM's structures.
shouldn't DWARF be expressive enough in most cases?
I agree that in order to understand a java.lang.String as a string, some such magic is agreeable, but then I don't really have to have it that comfy. Having gdb print array contents would be wonderful for now. :-) I'm asking about this on the gdb list as it is unrelated to gcj.
Best,
Michael
--
Dr. Michael Haupt
Principal Member of Technical Staff
Phone: +49 331 200 7277, Fax: +49 331 200 7561
Oracle Labs
Oracle Deutschland B.V. & Co. KG, Schiffbauergasse 14, 14467 Potsdam, Germany
prev parent reply other threads:[~2013-02-11 16:47 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
2013-02-11 16:26 ` Michael Haupt
2013-02-11 16:32 ` Andrew Haley
2013-02-11 16:47 ` Michael Haupt [this message]
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=0CF78145-71B2-43BC-BA56-DFE2159779FE@oracle.com \
--to=michael.haupt@oracle.com \
--cc=java@gcc.gnu.org \
/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).