From: Jim Wilson <wilson@specifixinc.com>
To: "Äåë÷î Äåëîâ" <ddelov@b.obs.bg>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC XML back end
Date: Wed, 21 Jan 2004 00:30:00 -0000 [thread overview]
Message-ID: <400DC830.8030205@specifixinc.com> (raw)
In-Reply-To: <400C00DF.9030500@b.obs.bg>
????? ????? wrote:
> Could You give me an advice about that, please. Do You use some tool
> when trace and debug GCC?
I use the emacs M-x gdb command. If you aren't an emacs user, you can
use gdb from the shell. Also, frequent use of grep and the more
involved "find . -type f | xargs grep" if I need to search subdirectories.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
prev parent reply other threads:[~2004-01-21 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 16:07 Делчо Делов
2004-01-21 0:30 ` Jim Wilson [this message]
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=400DC830.8030205@specifixinc.com \
--to=wilson@specifixinc.com \
--cc=ddelov@b.obs.bg \
--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).