public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "knoxj at att dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/35880] GNAT does not generate debugging information on imported entities
Date: Tue, 15 Apr 2008 13:32:00 -0000	[thread overview]
Message-ID: <20080415133104.28859.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35880-16034@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from knoxj at att dot net  2008-04-15 13:31 -------
I was going to update my bug report when I noticed Sam's comments. I used
"readelf -a -w test_pacs_cp_package.o" to try to see what was happening, and
I saw that the compiler was throwing out any information about the Ada
definintion. I would have expected the compiler to hang onto the Ada debug
information, but use the IMPORT information for code generation. The linker
would then resolve the IMPORT name, and the debugger could see the Ada
description. I too realized that shared memory was a red herring, and the real
problem was simply the IMPORT implementation. Sam's sample illustrates this
much better than the source files I submitted.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35880


      parent reply	other threads:[~2008-04-15 13:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  2:55 [Bug ada/35880] New: GNAT (GCC) Ada does not generate symbolic debug for shared memory knoxj at att dot net
2008-04-09  2:59 ` [Bug ada/35880] " knoxj at att dot net
2008-04-09  3:01 ` knoxj at att dot net
2008-04-09  6:46 ` charlet at gcc dot gnu dot org
2008-04-09 15:20 ` knoxj at att dot net
2008-04-09 15:26 ` charlet at adacore dot com
2008-04-09 16:19 ` knoxj at att dot net
2008-04-10  6:22 ` charlet at gcc dot gnu dot org
2008-04-14 20:05 ` [Bug ada/35880] GNAT does not generate debugging information on imported entities sam at gcc dot gnu dot org
2008-04-15 13:32 ` knoxj at att dot net [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=20080415133104.28859.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).