From: Andreas Schwab <schwab@suse.de>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: sashan <sashang@ihug.co.nz>, gcc@gcc.gnu.org
Subject: Re: [Newb] Stepping into cc1plus from gcc
Date: Sat, 20 Mar 2004 21:06:00 -0000 [thread overview]
Message-ID: <jeznabipqt.fsf@sykes.suse.de> (raw)
In-Reply-To: <orwu5gw248.fsf@livre.redhat.lsd.ic.unicamp.br> (Alexandre Oliva's message of "20 Mar 2004 01:53:27 -0300")
Alexandre Oliva <aoliva@redhat.com> writes:
> On Mar 20, 2004, sashan <sashang@ihug.co.nz> wrote:
>
>> I've been stepping through gcc and I've come the point, in
>> libiberty/pex-unix.c where it forks a new process called cc1plus. I'm
>> guessing this is the C++ compiler that is being called. Anyway I'd
>> like to know how to continue stepping into it.
>
> Add the attached scripts to your path and run:
>
> % debugx cc1plus g++ rest of command line
Try "gdb --args cc1plus ...".
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-03-20 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 9:06 sashan
2004-03-20 11:11 ` Phil Edwards
2004-03-23 22:47 ` [Newb] Stepping into gnat Sebastian Pop
2004-03-24 3:32 ` Laurent GUERBY
2004-03-20 11:17 ` [Newb] Stepping into cc1plus from gcc Alexandre Oliva
2004-03-20 21:06 ` Andreas Schwab [this message]
2004-03-21 18:15 ` Alexandre Oliva
2004-03-21 19:21 ` Andreas Schwab
2004-03-22 7:43 ` Alexandre Oliva
2004-03-22 13:57 ` llewelly
2004-03-23 11:29 ` Alexandre Oliva
2004-03-23 12:27 ` Tom Tromey
2004-03-23 12:52 ` sashan
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=jeznabipqt.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=sashang@ihug.co.nz \
/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).