From: Andi Kleen <andi@firstfloor.org>
To: Kevin Polulak <kpolulak@gmail.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Questions Regarding DWARF
Date: Thu, 08 Sep 2011 13:13:00 -0000 [thread overview]
Message-ID: <m2ipp35gau.fsf@firstfloor.org> (raw)
In-Reply-To: <CAHRX3kwY8C-Sj=Tmv6Hhk-Xn-63a0q8rixJyjXzu++BsjLcArg@mail.gmail.com> (Kevin Polulak's message of "Wed, 7 Sep 2011 21:59:07 -0400")
Kevin Polulak <kpolulak@gmail.com> writes:
>
> I've tried to gain some knowledge by digging through the GCC source
> but haven't come up with much other than the values of the DW_*
> constants which isn't that important. Are there any files in
> particular I should be looking at?
From the gcc internals manual:
* Debugging information output
This is run after final because it must output the stack slot
offsets for pseudo registers that did not get hard registers.
Source files are `dbxout.c' for DBX symbol table format,
`sdbout.c' for SDB symbol table format, `dwarfout.c' for DWARF
symbol table format, files `dwarf2out.c' and `dwarf2asm.c' for
DWARF2 symbol table format, and `vmsdbgout.c' for VMS debug symbol
table format.
-Andi
next prev parent reply other threads:[~2011-09-08 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 1:59 Kevin Polulak
2011-09-08 13:13 ` Andi Kleen [this message]
2011-09-08 15:09 ` Michael Eager
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=m2ipp35gau.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=gcc@gcc.gnu.org \
--cc=kpolulak@gmail.com \
/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).