From: Hari <hari@cse.iitb.ac.in>
To: gcc-help@gcc.gnu.org
Subject: Stack Trace with GCC
Date: Thu, 25 Mar 2004 18:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0403252055380.24204@mars.cse.iitb.ac.in> (raw)
Hi ,
I am an undergraduate student at IIT Bombay working on the control flow
of GCC while compiling c code.I am intrested in tracing the path of gcc
during compilation.I don't see any good material on this topic anywhere.
One approach is to put break points in all of (176) c files
in gcc directory and check the flow but that seems to be very time
consuming .
In response to my previous mail, Lars Segerlund
<lars.segerlund@comsys.se> suggested me of stack trace , but
I am not able to do so in a right way.So I am not getting the
complete trace.Is there any way out to get the complete stack trace???
--Hari
reply other threads:[~2004-03-25 15:32 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=Pine.LNX.4.58.0403252055380.24204@mars.cse.iitb.ac.in \
--to=hari@cse.iitb.ac.in \
--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).