From: Nagaraju Mekala <gnuuser.raj@gmail.com>
To: Michael Eager <eager@eagercon.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Issue with debug symbols with garbage collector
Date: Fri, 22 Apr 2022 11:59:38 +0530 [thread overview]
Message-ID: <CAKuVEhDF6zw2H15PLwXEvsfJzjJKZZ3KyQHVw0F4mfuM_D=EPw@mail.gmail.com> (raw)
In-Reply-To: <03fb076e-11a6-386c-4b63-957b226b4414@eagercon.com>
On Thu, Apr 21, 2022 at 11:58 PM Michael Eager <eager@eagercon.com> wrote:
> On 4/21/22 11:11, Michael Eager wrote:
> > On 4/21/22 00:27, Nagaraju Mekala via Gcc-help wrote:
> >>> I meant instead of pointing to _start, Debug symbols were pointing to
> >> microblaze_register_handler.
> >
> > Both symbols are at location 0.
> >
> >> I have attached the elf, where we cannot find any symbols related to
> >> microblaze_register_handler function but the debug_loc is somehow
> showing
> >> up at _start address.
> >
> > There are two places where symbols are defined. One is in the ELF
> > symbol table:
> >
> > $ readelf -s kc705_hello.elf | grep " _start"
> > 277: 0000000000000000 0 FUNC GLOBAL DEFAULT 1 _start
>
> There are a number of symbols with the prefix microblaze_ which appear
> in the ELF symbol table. I can't tell from the very limited information
> you provide why those are included but microblaze_register_handler is
> not. This probably has to do with how these functions are written.
>
Thanks for the information.
I will check why microblaze_register_handler is not part of symbol table.
-Nagaraju
>
> --
> Michael Eager
>
prev parent reply other threads:[~2022-04-22 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 9:15 Nagaraju Mekala
2022-04-20 19:22 ` Michael Eager
2022-04-21 7:27 ` Nagaraju Mekala
2022-04-21 18:11 ` Michael Eager
2022-04-21 18:28 ` Michael Eager
2022-04-22 6:29 ` Nagaraju Mekala [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='CAKuVEhDF6zw2H15PLwXEvsfJzjJKZZ3KyQHVw0F4mfuM_D=EPw@mail.gmail.com' \
--to=gnuuser.raj@gmail.com \
--cc=eager@eagercon.com \
--cc=gcc-help@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).