public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Dinn <adinn@redhat.com>
To: gdb-list <gdb@sourceware.org>
Subject: gcj debug question
Date: Tue, 25 Oct 2022 11:48:41 +0100	[thread overview]
Message-ID: <2932d319-9e73-53f1-0f97-bf2d67fdb879@redhat.com> (raw)

Hi gdb experts,

I'm hoping there is still enough institutional memory left somewhere in 
this forum to provide info about (the now defunct) DWARF support for 
gcj. Specifically, does anyone have a long enough memory to recall 
whether and, if so, how gcj advertised the presence of Java reflective 
class objects (instances of java.lang.Class) to the debugger?

   - Did it insert linker symbols for e.g. org.my.Foo.class into a 
generated binary?

   - Did it emit DWARF info records with tag DW_TAG_variable and 
associated attributes like name, type, linkage name and location?

   - In the latter case were these records located in the class (tag 
DW_TAG_class) info record or at top level in the same compile unit as 
the class?

Of course, the question assumes that java.lang.Class instances were 
present in the image heap in advance of startup, which may be completely 
unwarranted as they coudl equally be created on demand during program 
bootstrap or normal execution. Correction of any such erroneous 
presumption would be most welcome.

Answers on a (e-)postcard would be much appreciated. Actually, I'd be 
happy just with the name of someone who knows someone who might know.

regards,


Andrew Dinn
-----------


             reply	other threads:[~2022-10-25 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 10:48 Andrew Dinn [this message]
2022-11-09 16:10 ` Tom Tromey
2022-11-21 14:23   ` Andrew Dinn
2022-11-21 14:35     ` Jan Vrany

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=2932d319-9e73-53f1-0f97-bf2d67fdb879@redhat.com \
    --to=adinn@redhat.com \
    --cc=gdb@sourceware.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).