From: "Leon Taylor" <leon_taylor_007@yahoo.co.in>
To: gcc@gcc.gnu.org
Subject: Query about debug info
Date: Wed, 02 Apr 2003 09:32:00 -0000 [thread overview]
Message-ID: <20030402075030.44951.qmail@web8203.mail.in.yahoo.com> (raw)
Hi Everyone,
I am curious about debugging information generation
for user symbols. From dwarfout.c file, I could deduce
that DECL_RTL, PARM_DECL etc are some of the interface
used to output debug info. (I was looking
at location_or_const_value_attribute () function)
1) Is the same mechanism used for other debugging
formats too?
2) There are some cases in gcc/testsuite/debug
directory which scan generated assembly for "xyzzy"
string. I want to understand the rationale of those
test cases. To be specific let us consider
gcc.dg/debug/debug-6.c.
Why "xyzzy" occur in assembly output (with -g)?
and what if it doesn't come after some code
modification.(Which direction to explore ?)
Thanks and Regards,
Leon.
________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
visit http://in.tv.yahoo.com
reply other threads:[~2003-04-02 7:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030402075030.44951.qmail@web8203.mail.in.yahoo.com \
--to=leon_taylor_007@yahoo.co.in \
--cc=gcc@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).