From: Sergei <asita@hotbox.ru>
To: gcc-help@gcc.gnu.org
Subject: Re: Segmentation fault Causes
Date: Mon, 24 Feb 2003 08:00:00 -0000 [thread overview]
Message-ID: <20030224110824.0330309f.asita@hotbox.ru> (raw)
In-Reply-To: <2B721C6525F0D411B1E900B0D0226BDD02148F82@mohmsg01.ad.infosys.com>
On Mon, 24 Feb 2003 11:06:35 +0530
"Ajay Bansal" <Ajay_Bansal@infosys.com> wrote:
> John
>
> Can you please tell me how to use this fprintf(stderr... . ) function?
>
> Do I need to give it at many different places in the code??? If that is
> the case, what's is the difference between putting many different
> "cerr<<................"???
`fprintf' is from standard C library. `cerr <<' is from C++.
You may learn more about fprintf from `man fprintf'. Do #include <stdio.h> if you want to use it in your code.
Best regards,
Sergei
next prev parent reply other threads:[~2003-02-24 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 5:39 Ajay Bansal
2003-02-24 8:00 ` Sergei [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 5:07 Daniel Bolgheroni
2003-02-24 5:22 ` J.C.Wren
2003-04-22 1:02 ` Daniel Bolgheroni
2003-04-22 7:47 ` bjorn rohde jensen
2003-04-22 18:24 ` Dikandé Alain Moïse
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=20030224110824.0330309f.asita@hotbox.ru \
--to=asita@hotbox.ru \
--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).