From: "Yao qi" <qiyaobit@hotmail.com>
To: drizzle76@gmail.com, rafael.espindola@gmail.com
Cc: gcc@gcc.gnu.org
Subject: Re: how to compile gcc
Date: Mon, 22 Aug 2005 01:36:00 -0000 [thread overview]
Message-ID: <BAY12-F48A57429054ED3638E46BDFB60@phx.gbl> (raw)
In-Reply-To: <7326d8e405082006482db0467b@mail.gmail.com>
>From: drizzle drizzle <drizzle76@gmail.com>
>To: Rafael Ãvila de EspÃndola <rafael.espindola@gmail.com>
>CC: gcc@gcc.gnu.org
>Subject: Re: how to compile gcc
>Date: Sat, 20 Aug 2005 09:48:56 -0400
>
>If you are objective is to debug gcc, then all the necessary setup is
>already done...Check this documentation
> http://gcc.gnu.org/wiki/DebuggingGCC.
I have tried this method on wiki about GCC debugging. I am not sure about
that and mail the procedure here to verify it, maybe someone of you could
clarify for me. Thanks in advance.
Here goes the my procedure on GCC debugging.
1 Generate preprocessed source code wiht option -E and redirect to a file
named a.c.expand.
2 Debug cc1 by GDB with the arguments "-c a.c.expand" to cc1
Is this a reasonable procedure to debug GCC?
Any suggestion and comments are highly appreciated!
>
>dz
>
>On 8/20/05, Rafael Ãvila de EspÃndola <rafael.espindola@gmail.com> wrote:
> > http://gcc.gnu.org/install/configure.html
> > look at --enable-checking
> > and
> > http://gcc.gnu.org/install/build.html
> > There are more cflags...
> >
> > The gcc/Makefile.in is also a good reference :)
> >
> > > Thanks,
> > >
> > > -Jiang
> >
> >
> > Rafael
> >
Best Regards
----------------
Yao Qi
Bejing Institute of Technology
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
next prev parent reply other threads:[~2005-08-22 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 23:26 Jiang Long
2005-08-20 13:13 ` Rafael Ávila de Espíndola
2005-08-20 13:49 ` drizzle drizzle
2005-08-22 1:36 ` Yao qi [this message]
2005-08-22 1:36 ` Yao qi
2005-08-20 16:46 ` Mike Stump
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=BAY12-F48A57429054ED3638E46BDFB60@phx.gbl \
--to=qiyaobit@hotmail.com \
--cc=drizzle76@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=rafael.espindola@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).