This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Who generate .rela.debug_info?
- From: Nancy <nancydreaming at gmail dot com>
- To: Nathan Sidwell <nathan at acm dot org>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 19 Dec 2017 21:53:05 +0800
- Subject: Re: Who generate .rela.debug_info?
- Authentication-results: sourceware.org; auth=none
- References: <CADdyJmmV3ENy=8DnF4Abjn5KD7WU4hcsXM7tse4E1f7HF5JnUQ@mail.gmail.com> <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