public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nancy <nancydreaming@gmail.com>
To: Nathan Sidwell <nathan@acm.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Who generate .rela.debug_info?
Date: Tue, 19 Dec 2017 13:53:00 -0000	[thread overview]
Message-ID: <CADdyJm=aAyRJm6EHbCPGsQ2XbjL6e=_-UxKLoZ_j6j_OUwUMnA@mail.gmail.com> (raw)
In-Reply-To: <8220a6a0-ad34-31d2-d193-9d7330b506d9@acm.org>

> .rela.X is a relocation section generated by the assembler.  GCC emits debug
> information using assembler pseudos such as .word etc.  Those will name
> relocations.  The syntax for relocations is target-specific.  The above will
> be some_symbol@dtpoff or something.

Sorry, I did not find it in "AS". I did saw .text .data  .bss and some
other new segment created by "AS" through function "subseg_new", but I
could not find out where and how ".rela.debug_info" is generated. For
this case, "as" dwarf2dbg.c(binutils-2.29.1): 1932
if(emit_other_sections) does not run (emit_other_section==0).

My understand, all .debug_XXX is generated by GCC, "AS" just copy them
to obj, not a bit change. But I also could not find ".rela.X" in GCC.

Did I miss something?  I need a breakpoint to see "Oh it really
created it there~"

-- 
Best Regards,
Yu Rong Tan

  reply	other threads:[~2017-12-19 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 13:57 Nancy
2017-12-18 14:12 ` Nathan Sidwell
2017-12-19 13:53   ` Nancy [this message]
2017-12-19 13:59     ` Andreas Schwab
2017-12-19 14:03     ` Nathan Sidwell
2017-12-21 11:27       ` Nancy
2017-12-18 18:50 ` Michael Matz
2017-12-19 14:01   ` Nancy

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='CADdyJm=aAyRJm6EHbCPGsQ2XbjL6e=_-UxKLoZ_j6j_OUwUMnA@mail.gmail.com' \
    --to=nancydreaming@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=nathan@acm.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).